Getting 400 status, When trying to get Access Token

We are getting an API issue In Zoom.
We are using the OAuth2.0 to Authenticate the Zoom with our application. There sometimes when we trying to Authenticate Zoom we are getting a 400 status. This thing happen when we trying to get the Token first time by passing the CODE which sent from Zoom.


In fist time we going to Authenticate Zoom with our application it going to work, Then we disconnect it ( remove the previous authenticate credentials ) and going to authenticate again, In this time when passing the CODE to get the Token, we are getting 400 status from the ZOOM API. Even we tried multiple times this 400 status coming again and again.
After Sometime passed (1hr or more) then again we going to Authenticate it going to work without any issue.
This thing happen again and again, we didn’t able to find the root case for this issue.


400 Bad Request.
( Not getting more error info to get an Idea )

API Endpoints

URL use to get the CODE


After getting the CODE, we making the Initial Req to get Access-Token.

Req-Type: [POST]
host = ""
path = "/oauth/token"

// Req Header
headers =  {
    Accept: 'application/json',
    'Content-Type': 'application/x-www-form-urlencoded',
    Authorization: `Basic ${(Buffer.from(`${client.client_id}:${client.client_secret}`)).toString('base64')}`,

//Req Body
body = {
   code: initCode,
   redirect_uri: redirectURL,
   grant_type: 'authorization_code',
1 Like

Hi @devanuruddha ,

If this is periodically happening, please submit a support ticket and provide the following:

  • developer email associated with app
  • client id
  • tracking id(s) from the 400 Bad Request response headers

This way our service engineering team can track down the requests and see why they are sometimes failing

1 Like

Hi Gianni
Thank you for the Reply.

Sure i will make a support ticket and see.
That Tracking ID you mention, Is it’s value contain in this x-zm-trackingid key in Req Header ?

Yes exactly @devanuruddha :slight_smile:

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.