Auth Error while trying to create a meeting using Zoom API after shifting servers

Description/Error

We recently shifted servers from AWS to GoDaddy, keeping the domain and URL structure as is.

We’ve used the Zoom API to create a one-one meeting. However, we’re now getting the following error while requesting for a new access token using the refresh token:

{"reason":"Invalid request : token created error: Save Access token into Database error","error":"invalid_request"}array(2) { ["reason"]=> string(76) "Invalid request : token created error: Save Access token into Database error" ["error"]=> string(15) "invalid_request" }

We’ve maintained the same tokens (access and refresh token) as on the previous server. Can someone explain why this error may be occurring, and what one should do in order to resolve it?

Which Endpoint/s?
https://zoom.us/oauth/token’;

Additional context
I’m adding the PHP code that we’re using for the request (that we’re seeing the error after).

 //request zoom api for new access_token using refresh token
    $url = 'https://zoom.us/oauth/token';
    $postFields = http_build_query(array(
    'grant_type' => 'refresh_token',
    'client_id' => $clientId,
    'client_secret' => $clientSecret,
    'refresh_token' => $refreshToken
    ));

    $ch = curl_init();
    curl_setopt($ch, CURLOPT_URL,$url);
    curl_setopt($ch, CURLOPT_HTTPHEADER, array('Content-Type: application/x-www-form-urlencoded'));

    curl_setopt($ch, CURLOPT_RETURNTRANSFER,true);
    curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);
    curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, false);
    curl_setopt($ch, CURLOPT_POSTFIELDS, $postFields);
    $result = curl_exec($ch);
    //print_r($result); --> ERROR IS PRINTED HERE

Hi @Sneha_Arya,

Happy to help.

To investigate further on this issue, can you please provide us with the following:

  • Exact timestamps of when this error happened
  • Complete request sent to Zoom
  • Complete response received from Zoom.

Since there would be sensitive information involved in this, can you please send us a request on developersupport@zoom.us?

I will post the solution here once we diagnose and resolve the issue.

Thanks,
Ojus