# Randomly receiving "Invalid access token" for Server-to-Server OAuth

**URL:** <https://devforum.zoom.us/t/randomly-receiving-invalid-access-token-for-server-to-server-oauth/74432>\
**Category:** API and Webhooks\
**Tags:** oauth\
**Created:** [August 17, 2022, 9:24pm UTC](https://devforum.zoom.us/t/randomly-receiving-invalid-access-token-for-server-to-server-oauth/74432 "2022-08-17T21:24:46Z")\
**Posts on this page:** 1\
**Showing post:** 26

<div class="post-metadata">

**Author:** ![MultiplayerSession](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/multiplayersession/32/66446_2.png) [@MultiplayerSession](https://devforum.zoom.us/u/MultiplayerSession)\
**Post date:** [January 31, 2023, 4:41pm UTC](https://devforum.zoom.us/t/randomly-receiving-invalid-access-token-for-server-to-server-oauth/74432/26 "2023-01-31T16:41:32Z")

</div>

Developer Support limited me to [3 concurrent index values](https://devforum.zoom.us/t/server-to-server-oauth-annoying-token-invalidation/72070/8). If you need more than that, my recommendation is to create multiple identical Server-to-Server OAuth applications corresponding to the number of concurrent tokens you need (each application represents 1 index value).

---

_[View the full topic](https://devforum.zoom.us/t/randomly-receiving-invalid-access-token-for-server-to-server-oauth/74432)._