Open lautarodragan opened 5 years ago
Alternatively we may be able to keep the email in the token and ignore it.
But it's also duplicated information which could be outdated and cause strange issues.
The only remaining thing blocking this issue is letting the users know their API Keys will become obsolete and that they need to create new ones and use those instead.
Once that is done and this task is implemented, PATCH /accounts/:id { email: 'newemail@provider.com' }
will work as expected.
This may break stuff in Explorer. Needs research.