Server-to-Server OAuth App Returns Error 124 Invalid Access Token Despite Valid Credentials | Community
Skip to main content
C
Newcomer
Chris Kaplan
Newcomer
April 4, 2026
Solved

Server-to-Server OAuth App Returns Error 124 Invalid Access Token Despite Valid Credentials

  • April 4, 2026
  • 1 reply
  • 74 views

I have a Server-to-Server OAuth app that is activated and live on my account. When making API calls I receive error code 124 Invalid Access Token. I have verified my Account ID, Client ID, and Client Secret are correct and have regenerated the Client Secret multiple times. The app has the following scopes: meeting:write:meeting:admin, meeting:read:meeting:admin, user:read:user:admin, webinar:write:webinar:admin, webinar:read:webinar:admin. Please help me identify why the token is invalid.

Best answer by MGSR

Hello ​@Chris Kaplan,

Welcome to the Zoom Community! We’re glad to have you here.


This error typically means the access token used in your API request is invalid or expired. Here are some general steps to check:

  1. Ensure you are generating a new access token using the correct endpoint for Server-to-Server OAuth.
  2. Confirm that you are including the access token in the Authorization header as Bearer token in your API requests.
  3. Access tokens are short-lived; make sure you are not reusing an expired token.
  4. Double-check that your app is activated and the scopes match your API calls.
  5. If you are using a test environment, ensure you are not mixing credentials from different Zoom accounts or apps.

If you have verified all of the above and still receive error 124, it may be necessary to review your token generation process.

1 reply

MGSR
Community Manager
MGSRAnswer
Community Manager
April 8, 2026

Hello ​@Chris Kaplan,

Welcome to the Zoom Community! We’re glad to have you here.


This error typically means the access token used in your API request is invalid or expired. Here are some general steps to check:

  1. Ensure you are generating a new access token using the correct endpoint for Server-to-Server OAuth.
  2. Confirm that you are including the access token in the Authorization header as Bearer token in your API requests.
  3. Access tokens are short-lived; make sure you are not reusing an expired token.
  4. Double-check that your app is activated and the scopes match your API calls.
  5. If you are using a test environment, ensure you are not mixing credentials from different Zoom accounts or apps.

If you have verified all of the above and still receive error 124, it may be necessary to review your token generation process.

C
Newcomer
Chris KaplanAuthor
Newcomer
April 8, 2026

Thank you so much for your reply. I thought I deleted this because I soon figured out the error. One of the scopes I needed was incorrect. Thanks again!

    MGSR
    Community Manager
    MGSR
    Community Manager
    April 8, 2026

    You’re most welcome! We’re glad that your concern has been resolved. 
    Please feel free to reach out if you need any assistance. 

    Terms & ConditionsAccessibility statement
    Copyright © Zoom Communications, Inc. All rights reserved.