Refresh_token failure scenario assistance

[averypmcintyre (Avery)]

So from what I’ve gleaned from the documentation and this forum, the refresh_token is essentially one-time-use. When you use the refresh_token to request a new access_token then that refresh_token can no longer be used.

1. How should I handle a scenario like the following: a) get new access_token, b) utilize it synchronously, c) fail to persist the new refresh_token. It seems that my integration is now functionally in a “broken state” for this user.

2. Is there any way to get a behavior more akin to Google’s API where a refresh token can be used many times to receive a new access token?

[MaxM]

Hey @averypmcintyre,

Thank you for reaching out to the Zoom Developer Forum.

@averypmcintyre

How should I handle a scenario like the following: a) get new access_token , b) utilize it synchronously, c) fail to persist the new refresh_token . It seems that my integration is now functionally in a “broken state” for this user.

In this instance, the user would need to re-authorize the application. You could do this by sending them to the authorize URL again.

@averypmcintyre

Is there any way to get a behavior more akin to Google’s API where a refresh token can be used many times to receive a new access token?

We don’t currently have a method to accomplish this but we do have improvements to our OAuth offerings on the roadmap.

Thanks,
Max