# How to refresh token if refresh\_token in incorrect

**URL:** <https://devforum.zoom.us/t/how-to-refresh-token-if-refresh-token-in-incorrect/3338>\
**Category:** API and Webhooks\
**Created:** [February 20, 2019, 5:39pm UTC](https://devforum.zoom.us/t/how-to-refresh-token-if-refresh-token-in-incorrect/3338 "2019-02-20T17:39:25Z")\
**Posts on this page:** 16\
**Page:** 2

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [April 3, 2020, 10:29pm UTC](https://devforum.zoom.us/t/how-to-refresh-token-if-refresh-token-in-incorrect/3338/23 "2020-04-03T22:29:39Z")

</div>

Hey @katyle,

Indeed! Just let us know if you would like to increase the tolerance and for what app (I need the name). 🙂

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![katyle](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/katyle/32/1098_2.png) [@katyle](https://devforum.zoom.us/u/katyle)\
**Post date:** [April 3, 2020, 11:48pm UTC](https://devforum.zoom.us/t/how-to-refresh-token-if-refresh-token-in-incorrect/3338/24 "2020-04-03T23:48:58Z")

</div>

The name of the application is PowerSuite. Client ID: IZ4arx1eRkKAGfOxHvA

Katy

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [April 6, 2020, 4:21pm UTC](https://devforum.zoom.us/t/how-to-refresh-token-if-refresh-token-in-incorrect/3338/25 "2020-04-06T16:21:14Z")

</div>

Thanks @katyle,

We are reviewing your request (ZOOM-149706).

-Tommy

---

<div class="post-metadata">

**Author:** ![katyle](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/katyle/32/1098_2.png) [@katyle](https://devforum.zoom.us/u/katyle)\
**Post date:** [April 6, 2020, 6:11pm UTC](https://devforum.zoom.us/t/how-to-refresh-token-if-refresh-token-in-incorrect/3338/26 "2020-04-06T18:11:29Z")

</div>

Thank you Tommy. I’ll look for the final response.

Katy

---

<div class="post-metadata">

**Author:** ![muhammad.faizan.cs](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/muhammad.faizan.cs/32/4144_2.png) [@muhammad.faizan.cs](https://devforum.zoom.us/u/muhammad.faizan.cs)\
**Post date:** [April 6, 2020, 6:14pm UTC](https://devforum.zoom.us/t/how-to-refresh-token-if-refresh-token-in-incorrect/3338/27 "2020-04-06T18:14:58Z")

</div>

I have the same concerns really…

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [April 7, 2020, 5:14am UTC](https://devforum.zoom.us/t/how-to-refresh-token-if-refresh-token-in-incorrect/3338/28 "2020-04-07T05:14:29Z")

</div>

Will keep you updated!

-Tommy

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [April 7, 2020, 5:15am UTC](https://devforum.zoom.us/t/how-to-refresh-token-if-refresh-token-in-incorrect/3338/29 "2020-04-07T05:15:15Z")

</div>

Hey @muhammad.faizan.cs,

Please let us know if you have an issue first with refresh, then we can review upping your refresh tolerance.

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![rania.mohamed](https://avatars.discourse-cdn.com/v4/letter/r/71c47a/32.png) [@rania.mohamed](https://devforum.zoom.us/u/rania.mohamed)\
**Post date:** [April 15, 2020, 7:47pm UTC](https://devforum.zoom.us/t/how-to-refresh-token-if-refresh-token-in-incorrect/3338/30 "2020-04-15T19:47:38Z")

</div>

hey @tommy,  
when I get Access token by request of "refresh token " the response returned a new refresh token this means I should save the new returned refresh token with every request after 1 hour, but in the documentation, I found that the refresh token expires after 15 years  
how can I use only one refresh token without saving a new one every hour?

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [April 16, 2020, 5:53am UTC](https://devforum.zoom.us/t/how-to-refresh-token-if-refresh-token-in-incorrect/3338/31 "2020-04-16T05:53:32Z")

</div>

Hey @rania.mohamed,

Correct, the access\_token lasts 1 hour, and the refresh\_token lasts 15 years.

The proper flow is to **not** refresh the access\_token, **until** you need to make an api request, then you use the refresh\_token to get a new access\_token and refresh\_token, and then make the api request.

Instead of refreshing it every hour. 🙂

Does that make sense?

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![dhyun](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/dhyun/32/6753_2.png) [@dhyun](https://devforum.zoom.us/u/dhyun)\
**Post date:** [April 22, 2020, 6:03pm UTC](https://devforum.zoom.us/t/how-to-refresh-token-if-refresh-token-in-incorrect/3338/32 "2020-04-22T18:03:56Z")

</div>

@tommy Running into similar issues. A couple of questions:

1. What does it mean technically when you say “increase the tolerance”?
2. What is the process of asking for an increase in tolerance? Do we use this forum or send a request email?

Thanks

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [April 23, 2020, 5:20pm UTC](https://devforum.zoom.us/t/how-to-refresh-token-if-refresh-token-in-incorrect/3338/33 "2020-04-23T17:20:17Z")

</div>

Hey @dhyun,

Before we discuss about the refresh tolerance please share specific issues about the issue.

Make sure you are saving the latest refresh token properly each time you [issue a refresh request](https://marketplace.zoom.us/docs/guides/auth/oauth#refreshing).

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![dhyun](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/dhyun/32/6753_2.png) [@dhyun](https://devforum.zoom.us/u/dhyun)\
**Post date:** [April 23, 2020, 5:43pm UTC](https://devforum.zoom.us/t/how-to-refresh-token-if-refresh-token-in-incorrect/3338/34 "2020-04-23T17:43:42Z")

</div>

Hello @tommy,

We’re taking every precaution to store the new refresh token in Vault and in 99% (or more) of the cases this works perfectly fine. In those rare cases where the service crashes and is unable to contact our secure storage, we have a situation where we may lose the token. As our customers connect to Zoom via our application to monitor their account in a self-serve manner, it’s not feasible for us to contact them to ask them to re-onboard. As such, a little flexibility in terms of tolerance would go a long way to ensure a continuous operation of the monitoring.

Would be happy to provide more details or give you a demo. Thanks.

DSH

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [April 25, 2020, 12:58am UTC](https://devforum.zoom.us/t/how-to-refresh-token-if-refresh-token-in-incorrect/3338/35 "2020-04-25T00:58:54Z")

</div>

Thanks @dhyun,

Please let us know if this happens and we will be happy to see if we need to increase the tolerance.

> [@dhyun](#):
>
> it’s not feasible for us to contact them to ask them to re-onboard.

If you notice the connection has been broken, you could direct them to reauthorize your app programmatically by taking them to the [install url](https://marketplace.zoom.us/docs/guides/auth/oauth#getting-access-token). No need to manually contact them.

-Tommy

---

<div class="post-metadata">

**Author:** ![jerry2491](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jerry2491/32/59148_2.png) [@jerry2491](https://devforum.zoom.us/u/jerry2491)\
**Post date:** [May 8, 2020, 5:40am UTC](https://devforum.zoom.us/t/how-to-refresh-token-if-refresh-token-in-incorrect/3338/36 "2020-05-08T05:40:08Z")

</div>

I have same issue regarding refresh token. I am using PHP. I am facing following issue:-  
Fatal error: Uncaught GuzzleHttp\Exception\ClientException: Client error: `POST https://zoom.us/oauth/token` resulted in a `401 Unauthorized` response: {“reason”:“Invalid Token!”,“error”:“invalid\_request”}

When we try with authentication (from beginning) then it works fine. But after 1 hour when I try to refresh the token then it gives above error. There is some problem with the refresh token. Please guide me.

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [May 13, 2020, 12:35am UTC](https://devforum.zoom.us/t/how-to-refresh-token-if-refresh-token-in-incorrect/3338/37 "2020-05-13T00:35:19Z")

</div>

Hey @jerry2491,

Can you please private message me your refresh token?

Also make sure you are following the [refresh flow](https://marketplace.zoom.us/docs/guides/auth/oauth#refreshing).

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![DeveloperBot](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/developerbot/32/12632_2.png) [@DeveloperBot](https://devforum.zoom.us/u/DeveloperBot)\
**Post date:** [August 21, 2020, 9:17pm UTC](https://devforum.zoom.us/t/how-to-refresh-token-if-refresh-token-in-incorrect/3338/38 "2020-08-21T21:17:05Z")

</div>

Closed on August 21, 2020, 9:17pm UTC



[Previous page](https://devforum.zoom.us/t/how-to-refresh-token-if-refresh-token-in-incorrect/3338.md?page=1)
