# Multiple Refresh Tokens Support

**URL:** <https://devforum.zoom.us/t/multiple-refresh-tokens-support/138113>\
**Category:** Authentication\
**Created:** [October 17, 2025, 4:37pm UTC](https://devforum.zoom.us/t/multiple-refresh-tokens-support/138113 "2025-10-17T16:37:03Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![joey.grisafe](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/joey.grisafe/32/49146_2.png) [@joey.grisafe](https://devforum.zoom.us/u/joey.grisafe)\
**Post date:** [October 17, 2025, 4:37pm UTC](https://devforum.zoom.us/t/multiple-refresh-tokens-support/138113/1 "2025-10-17T16:37:03Z")

</div>

**API Endpoint(s) and/or Zoom API Event(s)**

- tokens oauth endpoint

**Description**  
The current functionality is to invalidate any preexisting refresh tokens when a new one is created. This makes it hard to test an application (in dev mode) across multiple environments. Or have different scoped tokens in the same application. I see there are multiple threads from the early 2020s asking about this that have gone stale. One mentions that this was a planned update, but it seems to never have come to fruition. Most oauth2 providers allow for multiple refresh tokens for the same user.

Is this still planned?

---

<div class="post-metadata">

**Author:** ![joey.grisafe](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/joey.grisafe/32/49146_2.png) [@joey.grisafe](https://devforum.zoom.us/u/joey.grisafe)\
**Post date:** [October 17, 2025, 4:37pm UTC](https://devforum.zoom.us/t/multiple-refresh-tokens-support/138113/2 "2025-10-17T16:37:56Z")

</div>

Here’s the mentioned previous post ID (since I can’t include links): 13560

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [October 23, 2025, 5:19pm UTC](https://devforum.zoom.us/t/multiple-refresh-tokens-support/138113/3 "2025-10-23T17:19:28Z")

</div>

Hi @joey.grisafe  
Thanks for reaching out to us.  
This is something that we are currently not working on and I dont think it’s currently in the roadmap