# Refresh token workflow for multi-tenant apps

**URL:** <https://devforum.zoom.us/t/refresh-token-workflow-for-multi-tenant-apps/79405>\
**Category:** API and Webhooks\
**Tags:** api-requests\
**Created:** [November 28, 2022, 10:35pm UTC](https://devforum.zoom.us/t/refresh-token-workflow-for-multi-tenant-apps/79405 "2022-11-28T22:35:26Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [November 29, 2022, 5:17pm UTC](https://devforum.zoom.us/t/refresh-token-workflow-for-multi-tenant-apps/79405/2 "2022-11-29T17:17:18Z")

</div>

You’ll want to implement your own key rotation strategy. I’ve outlined a proposed [two-key rotation strategy if you have a shared database](https://devforum.zoom.us/t/randomly-receiving-invalid-access-token-for-server-to-server-oauth/74432/15) that relies on exactly one process succeeding on an `UPDATE / WHERE` statement matching the original renewal time, but if you anticipate long periods of inactivity, you’ll additionally need to decide what the others should do while the winner is renewing the access token — maybe reschedule your process to rerun in a minute.

[I recommend creating duplicate applications](https://devforum.zoom.us/t/server-to-server-oauth-annoying-token-invalidation/72070/8) for however many concurrent tokens you need, but others have had success with asking Zoom Developer Support to increase the number of tokens per application.

---

_[View the full topic](https://devforum.zoom.us/t/refresh-token-workflow-for-multi-tenant-apps/79405)._