# How to protect against losing refresh\_token response

**URL:** <https://devforum.zoom.us/t/how-to-protect-against-losing-refresh-token-response/10375>\
**Category:** API and Webhooks\
**Created:** [March 31, 2020, 7:56pm UTC](https://devforum.zoom.us/t/how-to-protect-against-losing-refresh-token-response/10375 "2020-03-31T19:56:41Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![engineering1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/engineering1/32/4579_2.png) [@engineering1](https://devforum.zoom.us/u/engineering1)\
**Post date:** [March 31, 2020, 7:56pm UTC](https://devforum.zoom.us/t/how-to-protect-against-losing-refresh-token-response/10375/1 "2020-03-31T19:56:41Z")

</div>

**Description**  
refresh\_token may be lost by the network

**Error**  
The Zoom OAuth2 documentation [https://marketplace.zoom.us/docs/guides/auth/oauth#refreshing](https://marketplace.zoom.us/docs/guides/auth/oauth#refreshing)  
says “The latest refresh token must always be used for the next refresh request.”  
This way, if we make a request to get a new access token, and the request is successfully received by Zoom, and new tokens are issued, but on the way back there is a network failure, we would lose the new refresh token and the integration would no longer function correctly, through no fault of the user.

This would create a bad experience for the user, as they would be un-authenticated, and stop receiving updates, or be requested that they re-authenticate. They may associate with both Zoom and our application.

Do you have any workarounds for allowing retrying of the token\_refresh or do you plan to add an idempotent version of the API where we can protect against network errors.

**Which App Type (OAuth / Chatbot / JWT / Webhook)?**  
OAuth

**Which Endpoint/s?**  
/oauth/token?grant\_type=refresh\_token

**How To Reproduce (If applicable)**  
Steps to reproduce the behavior:

1. Configure OAuth App
2. Create a fake network error when refreshing a token
3. The app is now unauthorized, and it is impossible to retry the request

**Screenshots (If applicable)**

**Additional context**

---

_[View the full topic](https://devforum.zoom.us/t/how-to-protect-against-losing-refresh-token-response/10375)._
