# 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:** 6

<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:** [August 18, 2022, 5:29pm UTC](https://devforum.zoom.us/t/randomly-receiving-invalid-access-token-for-server-to-server-oauth/74432/6 "2022-08-18T17:29:51Z")

</div>

Are you saying that if I have multiple instances of my service running (as one would expect for a scalable, redundant application), that I can only have one valid `access_token` across all those instances? In other words, each time I call `https://zoom.us/oauth/token?grant_type=account_credentials&account_id=[account id]`, it invalidates the previous access token that was issued?

If this is the case, how are we supposed to build a clustered application that makes API requests in the Server-to-Server OAuth case? I don’t really want to have to keep the access token in a single place and try to synchronize it across all the instances of my application.

---

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