# Self increase of token index

**URL:** <https://devforum.zoom.us/t/self-increase-of-token-index/90883>\
**Category:** API and Webhooks\
**Tags:** api, s2s-oauth\
**Created:** [June 26, 2023, 1:59pm UTC](https://devforum.zoom.us/t/self-increase-of-token-index/90883 "2023-06-26T13:59:22Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![desautelsj](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/desautelsj/32/23584_2.png) [@desautelsj](https://devforum.zoom.us/u/desautelsj)\
**Post date:** [June 26, 2023, 2:51pm UTC](https://devforum.zoom.us/t/self-increase-of-token-index/90883/2 "2023-06-26T14:51:40Z")

</div>

According this [announcement](https://devforum.zoom.us/t/multi-access-tokens-launched-for-s2s-apps/90527), you no longer need to worry about OAuth tokens being invalidated by a subsequent request for another token. The purpose of the token index you are talking about was to overcome this particular problem and therefore the token index is no longer necessary. In fact, the announcement states that if you continue using the token index query parameter, it will simply be ignored.

---

_[View the full topic](https://devforum.zoom.us/t/self-increase-of-token-index/90883)._
