In the event you were to lose access to a valid
refresh_token for a user belonging to your namespace, you can recover an access to that user's data by asking a new authorization
code with the recover authorization code webservice.
Using this authorization
code, you'll be able to recover a valid
refresh_token, as described in the corresponding section of the documentation.
Although recovering access to your user's data using the recover authorization
code webservice can seem convenient, most of the time having to do so is the sign of an integration defect, most commonly:
- the integration does not replace former
refresh_tokenwith the new one, resulting at some point in the
refresh_tokenvalidity to expire.
- the integration might have instabilities that result in not correctly saving in database your newly
refresh_tokenfrom time to time. To get a full understanding on how to keep
refresh_tokenvalid so that you do not need to implement this webservice please refer to the dedicated documentation section.