# S2S OAuth Token invalid before 3600 seconds are over

**URL:** <https://devforum.zoom.us/t/s2s-oauth-token-invalid-before-3600-seconds-are-over/77858>\
**Category:** Meetings\
**Created:** [October 25, 2022, 9:35am UTC](https://devforum.zoom.us/t/s2s-oauth-token-invalid-before-3600-seconds-are-over/77858 "2022-10-25T09:35:59Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![david5](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/david5/32/40553_2.png) [@david5](https://devforum.zoom.us/u/david5)\
**Post date:** [October 25, 2022, 2:58pm UTC](https://devforum.zoom.us/t/s2s-oauth-token-invalid-before-3600-seconds-are-over/77858/2 "2022-10-25T14:58:44Z")

</div>

Do you have multiple instances of your application running at the same time (e.g. in a clustered environment)? You might be running into the undocumented “feature” where the previous OAuth token is invalidated when you request a new one.

> [@Randomly receiving "Invalid access token" for Server-to-Server OAuth](https://devforum.zoom.us/t/randomly-receiving-invalid-access-token-for-server-to-server-oauth/74432/22):
>
> For posterity and anyone else who happens to run across this thread while scratching their head about how Server-to-Server OAuth works: Requesting a new Server-to-Server OAuth token invalidates the previous one. Zoom can increase the “index” count for your account, allowing you to request different tokens with different indexes that do not interfere with each other (i.e. requesting a token for index 1 doesn’t invalidate the token requested for index 2). The token index is specified in the call…

---

_[View the full topic](https://devforum.zoom.us/t/s2s-oauth-token-invalid-before-3600-seconds-are-over/77858)._
