# Can same refresh token be used for multiple days until expiry for General Oauth APP

**URL:** <https://devforum.zoom.us/t/can-same-refresh-token-be-used-for-multiple-days-until-expiry-for-general-oauth-app/142693>\
**Category:** API and Webhooks\
**Created:** [March 31, 2026, 9:48pm UTC](https://devforum.zoom.us/t/can-same-refresh-token-be-used-for-multiple-days-until-expiry-for-general-oauth-app/142693 "2026-03-31T21:48:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sid1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/sid1/32/72923_2.png) [@Sid1](https://devforum.zoom.us/u/Sid1)\
**Post date:** [March 31, 2026, 9:48pm UTC](https://devforum.zoom.us/t/can-same-refresh-token-be-used-for-multiple-days-until-expiry-for-general-oauth-app/142693/1 "2026-03-31T21:48:43Z")

</div>

**API Endpoint(s) and/or Zoom API Event(s)**  
POST [https://zoom.us/oauth/token](https://zoom.us/oauth/token) (with grant\_type=refresh\_token)

**Description**  
I am using a **General OAuth App** (User-authorized OAuth 2.0) for a single service account.

My application architecture is as follows:

- Secrets Manager stores client\_id, client\_secret, and the current refresh\_token.

- We do **not** store the access\_token (it expires in 1 hour).

- A main CRUD Lambda reads the refresh\_token from Secrets Manager, calls the refresh endpoint to get a new access\_token, and uses it for API calls (create/delete/end meeting).

- A separate daily rotator Lambda runs at 3 AM to proactively refresh and update the refresh\_token in Secrets Manager.

I have observed through empirical testing that the **same refresh token can be successfully used multiple times** over multiple days to obtain new access tokens.

**Question:**  
According to the current Zoom behavior (2026), when I successfully call the refresh token endpoint:

- Is the **old refresh token** immediately invalidated, or can it still be used for some time?

- What is the official recommended best practice? Should we always store and use the **new refresh token** returned in the response on every refresh, or is it acceptable to keep using the same refresh token for a period of time?

**Error?**  
No specific error at the moment. This is more of a clarification / best practice question to make our token management robust.

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [April 2, 2026, 8:41am UTC](https://devforum.zoom.us/t/can-same-refresh-token-be-used-for-multiple-days-until-expiry-for-general-oauth-app/142693/2 "2026-04-02T08:41:26Z")

</div>

@Sid1 the refresh token is 1 time user. You will have to keep the new refresh token and repeat the process of requesting new access token + refresh token.
