# Request to increase OAuth token\_index tolerance

**URL:** <https://devforum.zoom.us/t/request-to-increase-oauth-token-index-tolerance/88278>\
**Category:** Authentication\
**Created:** [May 11, 2023, 6:38pm UTC](https://devforum.zoom.us/t/request-to-increase-oauth-token-index-tolerance/88278 "2023-05-11T18:38:07Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jlsingleton](https://avatars.discourse-cdn.com/v4/letter/j/3d9bf3/32.png) [@jlsingleton](https://devforum.zoom.us/u/jlsingleton)\
**Post date:** [May 11, 2023, 6:38pm UTC](https://devforum.zoom.us/t/request-to-increase-oauth-token-index-tolerance/88278/1 "2023-05-11T18:38:07Z")

</div>

Hi, I would like to request an increase to our OAuth token index tolerance to 2 for a server-to-server OAuth app called “Virtual Scheduler” (just created today on our account). The email that I created this account with is the one listed on this application. Thank you

---

<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:** [May 16, 2023, 5:07pm UTC](https://devforum.zoom.us/t/request-to-increase-oauth-token-index-tolerance/88278/3 "2023-05-16T17:07:12Z")

</div>

Hi @jlsingleton  
Thanks for reaching out to the Zoom Developer Forum, I am happy to help here!  
I have created a support ticket on your behalf and you should be hearing from our team soon.  
Cheers,  
Elisa

---

<div class="post-metadata">

**Author:** ![jlsingleton](https://avatars.discourse-cdn.com/v4/letter/j/3d9bf3/32.png) [@jlsingleton](https://devforum.zoom.us/u/jlsingleton)\
**Post date:** [May 16, 2023, 8:00pm UTC](https://devforum.zoom.us/t/request-to-increase-oauth-token-index-tolerance/88278/4 "2023-05-16T20:00:52Z")

</div>

Hi Elisa, Thank you so much! I have not located any zoom documentation or examples within the OAuth2.0 Framework (rfc6749) of how to utilize the token\_index. We have proof of concepts working with the default single token index, but can you point me in the right direction for an example when more than 1 token index is being used? Thank you!

---

<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:** [May 19, 2023, 12:24pm UTC](https://devforum.zoom.us/t/request-to-increase-oauth-token-index-tolerance/88278/5 "2023-05-19T12:24:20Z")

</div>

Hey @john  
We are working on creating the docs for this feature and releasing them, I will make sure to share them with you when they are live.  
In the meantime, if you already have a higher token tolerance in your app, the main thing that changes is just an extra query parameter in your request when requesting an Oauth token.  
For example:  
[https://zoom.us/oauth/token?grant\_type=account\_credentials&account\_id={accountId}&token\_index=0](https://zoom.us/oauth/token?grant_type=account_credentials&account_id=%7BaccountId%7D&token_index=0)  
This request will generate a token in index 0, so you can go ahead and send a second request like this:  
[https://zoom.us/oauth/token?grant\_type=account\_credentials&account\_id={accountId}&token\_index=1](https://zoom.us/oauth/token?grant_type=account_credentials&account_id=%7BaccountId%7D&token_index=1)  
this will generate another token at index 1, the importance of this feature is that token at index 0 won’t be invalidated and you will be able to have 2 tokens working at the same time.

The default behavior is that when you create a new token, the previous one gets invalidated.  
Hope this helps!  
Elisa