# Multiple access tokens for zoom api **URL:** \ **Category:** Webinars\ **Created:** [January 16, 2023, 6:10am UTC](https://devforum.zoom.us/t/multiple-access-tokens-for-zoom-api/81495 "2023-01-16T06:10:14Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![gaurav.gupta1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gaurav.gupta1/32/60314_2.png) [@gaurav.gupta1](https://devforum.zoom.us/u/gaurav.gupta1)\ **Post date:** [January 16, 2023, 6:10am UTC](https://devforum.zoom.us/t/multiple-access-tokens-for-zoom-api/81495/1 "2023-01-16T06:10:14Z")
Hello, We are using web and android sdk for hosing webinars in our application. Currently, we are making api calls to zoom using the endpoint for token generation. The issue we are facing is whenever a new access token is generated, the old one gets invalidated, due to which we are facing unauthorized access quite frequently. Therefore, I request you to provide us multiple access tokens and guide me on how to acquire the same. Please look into this on priority as this is affecting our business. ---
**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:** [January 18, 2023, 2:38am UTC](https://devforum.zoom.us/t/multiple-access-tokens-for-zoom-api/81495/2 "2023-01-18T02:38:43Z")
Hi @gaurav.gupta1 Thanks for reaching out to the Zoom Developer Forum, I am happy to help here! Could you please confirm what app type are you using to generate the tokens so I can understand your issue better? Best, Elisa ---
**Author:** ![gaurav.gupta1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gaurav.gupta1/32/60314_2.png) [@gaurav.gupta1](https://devforum.zoom.us/u/gaurav.gupta1)\ **Post date:** [January 18, 2023, 10:00am UTC](https://devforum.zoom.us/t/multiple-access-tokens-for-zoom-api/81495/3 "2023-01-18T10:00:06Z")
Hi elisa, I am using server to server app with event notifications enabled. ---
**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:** [January 18, 2023, 9:06pm UTC](https://devforum.zoom.us/t/multiple-access-tokens-for-zoom-api/81495/4 "2023-01-18T21:06:14Z")
Hi @gaurav.gupta1 Thanks for confirming that with me. I just want to confirm that the issue that you are seeing is expected. When generating a token with the Server-to-Server Oauth app, this will be valid for 1 hour, but if you generate a new one, the previous one will be invalidated and this is the expected behavior. ---
**Author:** ![gaurav.gupta1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gaurav.gupta1/32/60314_2.png) [@gaurav.gupta1](https://devforum.zoom.us/u/gaurav.gupta1)\ **Post date:** [January 19, 2023, 8:27am UTC](https://devforum.zoom.us/t/multiple-access-tokens-for-zoom-api/81495/5 "2023-01-19T08:27:03Z")
Okay, but can I be provided multiple access tokens to manage this? ---
**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:** [January 19, 2023, 3:18pm UTC](https://devforum.zoom.us/t/multiple-access-tokens-for-zoom-api/81495/6 "2023-01-19T15:18:30Z")
Hi @gaurav.gupta1 We do have a workaround for this and it is to increase the token\_index tolerance for your application. So you can generate tokens at different indexes. For example, you request a token\_index 1 and then another one at token\_index 2, so the token generated at token\_index 2 won’t invalidate the token\_ index 1. If you would like to get this token\_index increase in your Server to Server OAuth app, feel free to reach out to our support team with a link to this thread and they will help you from there: [https://support.zoom.us/hc/en-us/requests/new](https://support.zoom.us/hc/en-us/requests/new) Best, Elisa ---
**Author:** ![cgoh1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/cgoh1/32/72973_2.png) [@cgoh1](https://devforum.zoom.us/u/cgoh1)\ **Post date:** [April 27, 2023, 1:21pm UTC](https://devforum.zoom.us/t/multiple-access-tokens-for-zoom-api/81495/7 "2023-04-27T13:21:04Z")
Is there any documention on how this token\_index works? Do you request per specific app? How do you guarantee one environment uses token\_index 1, 2nd enrvironment uses token\_index 2? ---
**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:** [April 28, 2023, 1:11pm UTC](https://devforum.zoom.us/t/multiple-access-tokens-for-zoom-api/81495/8 "2023-04-28T13:11:04Z")
Hi @cgoh1 This is an app-level increase, so if you want to request this for more than one app this is done per app. you will have to programmatically make sure that you are assigning the tokens correctly in your different environments. How this works is that you generate acces\_token at different indexes and the creation of them won’t invalidate the previous one. When you generate the first token\_index=0 and right after that token\_index=1, the first token will be valid even though you have generated a second one ---
**Author:** ![cgoh1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/cgoh1/32/72973_2.png) [@cgoh1](https://devforum.zoom.us/u/cgoh1)\ **Post date:** [April 28, 2023, 6:37pm UTC](https://devforum.zoom.us/t/multiple-access-tokens-for-zoom-api/81495/9 "2023-04-28T18:37:04Z")
> [@elisa.zoom](#): > > Hi @cgoh1 > This is an app-level increase, so if you want to request this for more than one app this is done per app. And we’d request via a support ticket referencing the app by name? or client\_id? or url? My ticket is [Home - Zoom Support](https://support.zoom.us/hc/en-us/requests/17123194) ---
**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 1, 2023, 1:37pm UTC](https://devforum.zoom.us/t/multiple-access-tokens-for-zoom-api/81495/10 "2023-05-01T13:37:13Z")
Hey @cgoh1 Make sure to share the app name and client ID of your app ---
**Author:** ![cgoh1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/cgoh1/32/72973_2.png) [@cgoh1](https://devforum.zoom.us/u/cgoh1)\ **Post date:** [May 1, 2023, 1:55pm UTC](https://devforum.zoom.us/t/multiple-access-tokens-for-zoom-api/81495/11 "2023-05-01T13:55:55Z")
Will do. I thought the URL would be enough. ---
**Author:** ![cgoh1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/cgoh1/32/72973_2.png) [@cgoh1](https://devforum.zoom.us/u/cgoh1)\ **Post date:** [May 16, 2023, 5:58pm UTC](https://devforum.zoom.us/t/multiple-access-tokens-for-zoom-api/81495/12 "2023-05-16T17:58:25Z")
The zoom ticket took a while to percolate, but they finally got it so we can use token\_index. ---
**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, 6:28pm UTC](https://devforum.zoom.us/t/multiple-access-tokens-for-zoom-api/81495/13 "2023-05-16T18:28:41Z")
Glad that work out! @cgoh1