# Frequent invalid token requests **URL:** \ **Category:** API and Webhooks\ **Created:** [May 30, 2021, 12:48pm UTC](https://devforum.zoom.us/t/frequent-invalid-token-requests/51376 "2021-05-30T12:48:58Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![fahad.beehive](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/fahad.beehive/32/17024_2.png) [@fahad.beehive](https://devforum.zoom.us/u/fahad.beehive)\ **Post date:** [May 30, 2021, 12:48pm UTC](https://devforum.zoom.us/t/frequent-invalid-token-requests/51376/1 "2021-05-30T12:48:58Z")
Apologies for opening another topic but the topic got closed: > [@Frequently receiving invalid\_request / token revocation from Zoom](https://devforum.zoom.us/t/frequently-receiving-invalid-request-token-revocation-from-zoom/44220/23): > > We appreciate the feedback, Fahad. We will continue to keep you posted on new developments. Best, Will This is still the number one complaint we receive daily. Is there any news on a fix? Thanks ---
**Author:** ![MaxM](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/maxm/32/42303_2.png) [@MaxM](https://devforum.zoom.us/u/MaxM)\ **Post date:** [June 2, 2021, 12:01am UTC](https://devforum.zoom.us/t/frequent-invalid-token-requests/51376/2 "2021-06-02T00:01:50Z")
Hey @fahad.beehive, Thank you for reaching out to the Zoom Developer Forum. I don’t have any new information on the issue just yet. I’ve reached out to our engineering team to see if they can provide an update. I’ll let you know what I hear. Thanks, Max ---
**Author:** ![fahad.beehive](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/fahad.beehive/32/17024_2.png) [@fahad.beehive](https://devforum.zoom.us/u/fahad.beehive)\ **Post date:** [June 4, 2021, 5:52pm UTC](https://devforum.zoom.us/t/frequent-invalid-token-requests/51376/3 "2021-06-04T17:52:27Z")
Thanks Max. Need I repeat - this is causing a lot of stress, wasted support hours and a time waste since each app that connects to Zoom across two or more devices continues to invalidate the token. Switching from one device back to another, you’re greeted with a “Authorize app to use Zoom” again. ---
**Author:** ![MaxM](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/maxm/32/42303_2.png) [@MaxM](https://devforum.zoom.us/u/MaxM)\ **Post date:** [June 7, 2021, 9:36pm UTC](https://devforum.zoom.us/t/frequent-invalid-token-requests/51376/4 "2021-06-07T21:36:54Z")
Hey @fahad.beehive, Thank you for communicating how critical this is for you. We might be able to increase the token expiry tolerance for your app to address this, at least partially, in the meantime. Please send an email to [developersupport@zoom.us](mailto:developersupport@zoom.us) with a link to this thread. I’ll follow up with you there. Thanks, Max ---
**Author:** ![fahad.beehive](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/fahad.beehive/32/17024_2.png) [@fahad.beehive](https://devforum.zoom.us/u/fahad.beehive)\ **Post date:** [June 7, 2021, 10:02pm UTC](https://devforum.zoom.us/t/frequent-invalid-token-requests/51376/5 "2021-06-07T22:02:11Z")
Thanks Max - that would be great, however I don’t think that would help though, since it expires only after you sign into another device, i.e. the existing token invalidates and the moment our app on the first device tries to connect, it’s greeted with an invalid\_token response. Or are you suggesting that the invalidation can be extended? ---
**Author:** ![MaxM](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/maxm/32/42303_2.png) [@MaxM](https://devforum.zoom.us/u/MaxM)\ **Post date:** [June 9, 2021, 4:43pm UTC](https://devforum.zoom.us/t/frequent-invalid-token-requests/51376/6 "2021-06-09T16:43:50Z")
Hey @fahad.beehive, Currently, our OAuth apps only allow one valid access\_token at a time which is why you’ll see that requesting a new access\_token on another device invalidates the first one. On a case-by-case basis, depending heavily on need and on the use case, we have a couple of options we can look into to potentially mitigate this behavior. If that sounds like something you want to look into, please send in an email. Any information you can provide about your use case there will help me to understand the best route forward and engage the proper team, if necessary. Thanks, Max ---
**Author:** ![fahad.beehive](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/fahad.beehive/32/17024_2.png) [@fahad.beehive](https://devforum.zoom.us/u/fahad.beehive)\ **Post date:** [June 9, 2021, 4:58pm UTC](https://devforum.zoom.us/t/frequent-invalid-token-requests/51376/7 "2021-06-09T16:58:01Z")
Thank you! Already sent the email 🙂 ---
**Author:** ![MaxM](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/maxm/32/42303_2.png) [@MaxM](https://devforum.zoom.us/u/MaxM)\ **Post date:** [June 10, 2021, 10:52pm UTC](https://devforum.zoom.us/t/frequent-invalid-token-requests/51376/8 "2021-06-10T22:52:34Z")
Hey @fahad.beehive, Thank you for submitting a ticket, I’ll follow up with you there. Thanks, Max ---
**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\ **Post date:** [July 11, 2021, 8:53am UTC](https://devforum.zoom.us/t/frequent-invalid-token-requests/51376/9 "2021-07-11T08:53:29Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.