# Known Zoom API issues **URL:** \ **Category:** API and Webhooks\ **Created:** [December 24, 2019, 9:01pm UTC](https://devforum.zoom.us/t/known-zoom-api-issues/7207 "2019-12-24T21:01:34Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\ **Post date:** [December 24, 2019, 9:01pm UTC](https://devforum.zoom.us/t/known-zoom-api-issues/7207/1 "2019-12-24T21:01:34Z")
If you are experiencing an “Invalid Token” error, there is a possibility it is a bug on Zoom’s end. Below are details of the bug, a **work around** , and when we are releasing a fix: Conditions: This problem can arise when a token is granted and then immediately used to call a Zoom API endpoint. The server that issues the new token sets the nbf (not valid before) time to be the time “exactly now.” But not all servers at Zoom have synchronized clocks. If the token is immediately used for an API endpoint that is on a different server, that server’s local clock may be up to a second too slow, with a time before the token’s nbf time, causing the server to reject the token. This bug applies to: - All token requests: Both original token grants, and refresh grants. - All tokens: that includes JWT tokens, as well as OAuth tokens of both grant types: authorization\_code and client\_credentials. Reproducibility: This problem is either 0% or 90% reproducible: it depends how the Zoom load balancer forwards API requests to Zoom servers. It can happen either all the time, or not at all, depending on your source IP address. Fix time: We will have a fix that will roll out in an upcoming release. Work-around: After acquiring a token, wait 1 second before using it. Related topic: > [@Refresh token request failing with 401](https://devforum.zoom.us/t/refresh-token-request-failing-with-401/6447/48): > > Hey @tsykul, @nathan.arora, @alon, @roy, @shane.zoom, @ps40, Here are updates on the Invalid Token bug: Conditions: This problem can arise when a token is granted and then immediately used to call a Zoom API endpoint. The server that issues the new token sets the nbf (not valid before) time to be the time “exactly now.” But not all servers at Zoom have synchronized clocks. If the token is immediately used for an API endpoint that is on a different server, that server’s local clock may be … Thanks, Tommy ---
**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\ **Post date:** [December 24, 2019, 9:02pm UTC](https://devforum.zoom.us/t/known-zoom-api-issues/7207/2 "2019-12-24T21:02:06Z")
---
**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\ **Post date:** [January 2, 2020, 9:56pm UTC](https://devforum.zoom.us/t/known-zoom-api-issues/7207/3 "2020-01-02T21:56:51Z")
---
**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\ **Post date:** [January 6, 2020, 8:10pm UTC](https://devforum.zoom.us/t/known-zoom-api-issues/7207/4 "2020-01-06T20:10:10Z")
UDPATE: Fixed on Sunday Jan 5th. Thanks, Tommy ---
**Author:** ![DeveloperBot](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/developerbot/32/12632_2.png) [@DeveloperBot](https://devforum.zoom.us/u/DeveloperBot)\ **Post date:** [August 21, 2020, 7:09pm UTC](https://devforum.zoom.us/t/known-zoom-api-issues/7207/5 "2020-08-21T19:09:07Z")