# ServerToServer API App

**URL:** <https://devforum.zoom.us/t/servertoserver-api-app/78548>\
**Category:** Authentication\
**Created:** [November 9, 2022, 4:13pm UTC](https://devforum.zoom.us/t/servertoserver-api-app/78548 "2022-11-09T16:13:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dshishkov](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/dshishkov/32/42874_2.png) [@dshishkov](https://devforum.zoom.us/u/dshishkov)\
**Post date:** [November 9, 2022, 4:13pm UTC](https://devforum.zoom.us/t/servertoserver-api-app/78548/1 "2022-11-09T16:13:40Z")

</div>

Hello,

We are experiencing an issue somewhat described here [Server-to-Server Oath token only one available at a given point in time?](https://devforum.zoom.us/t/server-to-server-oath-token-only-one-available-at-a-given-point-in-time/75351)

In our company’s Zoom account we have ServerToServer apps setup under different user accounts. Each app is setup under a separate user. We are noticing a behavior where if user A issues an accessToken for their app and then user B issues an accessToken for their app, the user A accessToken is invalidated. Shouldn’t the accessToken be per user so that user are not invalidating each other’s accessTokens?

Any help is appreciated!

---

<div class="post-metadata">

**Author:** ![brandon.abajelo](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/brandon.abajelo/32/39183_2.png) [@brandon.abajelo](https://devforum.zoom.us/u/brandon.abajelo)\
**Post date:** [November 10, 2022, 6:08pm UTC](https://devforum.zoom.us/t/servertoserver-api-app/78548/2 "2022-11-10T18:08:40Z")

</div>

@dshishkov when a server-to-server token is generated, it invalidates previous tokens by design. However, we do have an alternative option for developers who really need multiple tokens in parallel. Please create a ticket with our [dev support](https://devsupport.zoom.us/hc/en-us) site explaining your use case and we can assist!