# Refresh\_token failure scenario assistance

**URL:** <https://devforum.zoom.us/t/refresh-token-failure-scenario-assistance/52427>\
**Category:** API and Webhooks\
**Created:** [June 14, 2021, 7:41pm UTC](https://devforum.zoom.us/t/refresh-token-failure-scenario-assistance/52427 "2021-06-14T19:41:59Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![averypmcintyre](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/averypmcintyre/32/28093_2.png) [@averypmcintyre](https://devforum.zoom.us/u/averypmcintyre)\
**Post date:** [June 14, 2021, 7:41pm UTC](https://devforum.zoom.us/t/refresh-token-failure-scenario-assistance/52427/1 "2021-06-14T19:41:59Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![MaxM](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/maxm/32/42303_2.png) [@MaxM](https://devforum.zoom.us/u/MaxM)\
**Post date:** [June 15, 2021, 9:52pm UTC](https://devforum.zoom.us/t/refresh-token-failure-scenario-assistance/52427/2 "2021-06-15T21:52:56Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [July 16, 2021, 7:53am UTC](https://devforum.zoom.us/t/refresh-token-failure-scenario-assistance/52427/3 "2021-07-16T07:53:26Z")

</div>

Closed on July 16, 2021, 7:53am UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
