# Server to Server OAuth tokens and concurrent usage (e.g. web apps)

**URL:** <https://devforum.zoom.us/t/server-to-server-oauth-tokens-and-concurrent-usage-e-g-web-apps/76278>\
**Category:** API and Webhooks\
**Tags:** server-to-server\
**Created:** [September 20, 2022, 8:59pm UTC](https://devforum.zoom.us/t/server-to-server-oauth-tokens-and-concurrent-usage-e-g-web-apps/76278 "2022-09-20T20:59:02Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![shawnthomas](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/shawnthomas/32/36754_2.png) [@shawnthomas](https://devforum.zoom.us/u/shawnthomas)\
**Post date:** [September 20, 2022, 9:13pm UTC](https://devforum.zoom.us/t/server-to-server-oauth-tokens-and-concurrent-usage-e-g-web-apps/76278/3 "2022-09-20T21:13:07Z")

</div>

I found this: [Randomly receiving “Invalid access token” for Server-to-Server OAuth - API and Webhooks - Zoom Developer Forum](https://devforum.zoom.us/t/randomly-receiving-invalid-access-token-for-server-to-server-oauth/74432/20), for anyone else looking. But looks like basically yes, we need to introduce a token manager-type function into our backend so the rest of our app business logic doesn’t have to be concerned with it.

---

_[View the full topic](https://devforum.zoom.us/t/server-to-server-oauth-tokens-and-concurrent-usage-e-g-web-apps/76278)._