Refresh token request failing with 401

[ncsquared]

@ps40

grant_type=refresh_token&refresh_token=

@tommy also experiencing this issue. DMing details to you. Thanks for all the help lately

[tommy (Tommy Gaessler)]

You are welcome!

Thanks for sending details, we are looking into this. (ZOOM-148612)

-Tommy

[mattpegler]

Hi @tommy, we have 6 examples of this error from recent days. We lock while updating Zoom access tokens, so we are confident we are using the most recent refresh token. Would you like additional examples to help debug?

Edit: the access token is valid for the hour, as expected, but we get a 401 when trying to generate a new access token from our refresh token.

[tommy (Tommy Gaessler)]

Hey @mattpegler,

Apologies you are running into this issue.

Can you private message me your most recent access_token and refresh_token and Client ID so I can debug?

Thanks,
Tommy

[tommy (Tommy Gaessler)]

Hey @jford,

After looking into the logs, we have found that the issue is because the user uninstalled the application, so the token has been revoked

The user installed it on Mar 31, 2020 @ 20:27:35.183 (UTC) and uninstalled it on Mar 31, 2020 @ 21:31:42.850. And you got the error on Apr 1, 2020 @ 16:00:44.168.

Hey @ncsquared,

After looking into the logs, we have found that the issue is because you authorized the application twice but only hold the OAuth token from the first authorization

You authorized the application on Mar 26, 2020 @ 19:04:09.421 (UTC) and authorized the application again on Mar 26, 2020 @ 19:18:02.489. And you hold the token from first authorization. But these tokens will be revoked when the user authorize the application again. Make sure to save the latest tokens when re authorizing or refreshing the access_token.

Thanks,
Tommy

[jford (James)]

Hey @tommy,

I got the error while the app was installed. The error time you mentioned is over a day after I posted you the error details.

Thanks,
James

[ncsquared]

Sharing in hopes this helps others on this thread…

I’ve been calling the API using Content-Type: application/json and a json payload to refresh the token. This is rejected by Zoom’s OAuth server with the error 401 { code: 124, message: 'invalid access token' }, which is the same error given, when using a bad refresh token.

I switched my code to use application/x-www-form-urlencoded, and it works like a charm.

@tommy the API docs section on OAuth doesn’t have an example request for token refresh. Because I’m an OAuth n00b, I assumed this endpoint will accept JSON posts like the rest of the API… Another doc improvement for your trello/jira/dev/null or a feature request for a different error message when the Content-Type is wrong

[tommy (Tommy Gaessler)]

Hey @ncsquared,

Strange, it should work with a type application JSON request too.

Here are the refresh docs: https://marketplace.zoom.us/docs/guides/auth/oauth#refreshing

Thanks,
Tommy

[tommy (Tommy Gaessler)]

Hey @jford,

Strange. Can you try the install flow again and see if that fixes it?

Thanks,
Tommy

[ncsquared]

@tommy good to know about this page. I thought this was the reference page https://marketplace.zoom.us/docs/api-reference/using-zoom-apis

[tommy (Tommy Gaessler)]

Happy to help!

-Tommy

[asif]

Hi Tommy,
I am getting this error
{
“reason”: “Invalid Token!”,
“error”: “invalid_request”
}

and here is my URL https://zoom.us/oauth/token?grant_type=refresh_token&refresh_token={refersh Token}

In header
Authorization Basic base64Encode (Client_ID:Client_Secret)
Please help me to resolve this

Thanks,

[picktime (PTAdmin)]

Hi I’m getting this error ’ {“reason”:“Invalid Token!”,“error”:“invalid_request”} ’ for some reason which was working before. All of a sudden all of our users are reporting that zoom integration is not working. Please respond asap.

[tommy (Tommy Gaessler)]

Hey @asif,

Please make sure you are making a POST request and not a GET request.

Thanks,
Tommy

[tommy (Tommy Gaessler)]

Hey @picktime,

I will respond to you in your other thread:

"Invalid Token!" error message when trying to refresh oauth token

Hi @tommy We confirm that we are not using GET. We are using only POST. It is working in development with dev client id & secret. It’s just not working in live. We are pretty sure that we are using live client id and secret and we are using POST. Everything seems to work except generating new access token with the latest refresh token. Can you please resolve this asap.

Thanks,
Tommy

[picktime (PTAdmin)]

Hi @tommy

Please can you verify the issue asap. We have been waiting on it for last 1 week. Please let us know if there is any update.

[picktime (PTAdmin)]

Hi @tommy

Is there a way to directly get in touch with you?

[michael.zoom (Michael)]

For future note - We’re currently investigating with other users in the thread Tommy linked above

[randers (Ricardo)]

We have the same issue - is there any update?

[tommy (Tommy Gaessler)]

For others reference, here is the solution to @picktime’s issue:

"Invalid Token!" error message when trying to refresh oauth token

Happy to help @picktime! In case this can help others, Picktime’s issue was an empty space in the authorize url between the client_id and redirect_url query param: https://zoom.us/oauth/authorize?response_type=code&client_id={client_id} &redirect_uri={redirect_url} -Tommy

Thanks,
Tommy