# Code 124 - Requests failing despite 200 response for access token **URL:** \ **Category:** API and Webhooks\ **Tags:** api\ **Created:** [November 4, 2022, 3:30pm UTC](https://devforum.zoom.us/t/code-124-requests-failing-despite-200-response-for-access-token/78312 "2022-11-04T15:30:18Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![donte.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/donte.zoom/32/24412_2.png) [@donte.zoom](https://devforum.zoom.us/u/donte.zoom)\ **Post date:** [November 4, 2022, 6:28pm UTC](https://devforum.zoom.us/t/code-124-requests-failing-despite-200-response-for-access-token/78312/4 "2022-11-04T18:28:18Z")
Thanks for the additional context. It sounds like the behavior may have been a by-product of the major data error you mentioned. Is that accurate? Generally, I see the “Invalid access token ” when making subsequent to get an access token. This is because each time you call to get an access token, it invalidates the previous access token that was issued. To prevent this, you can submit a support request to increase the index tolerance, you will be able to generate tokens at different indexes so the tokens won’t get invalidated. Here is the post with more details on this topic you can check out : > [@Randomly receiving "Invalid access token" for Server-to-Server OAuth](https://devforum.zoom.us/t/randomly-receiving-invalid-access-token-for-server-to-server-oauth/74432): > > Starting this week, we have started receiving a lot of errors when calling Zoom APIs with our Server-to-Server OAuth token. { "code": 124, "message": Invalid access token." } When I look at the access token in question, it has not expired…there’s plenty of time left. We also have logic in place to refresh the token well before it’s scheduled to expire. Has something changed about the way Server-to-Server OAuth access tokens are managed on the Zoom side? We’ve had to put in a retry mechanism… Let me know if this helps. --- _[View the full topic](https://devforum.zoom.us/t/code-124-requests-failing-despite-200-response-for-access-token/78312)._