The same issue I’m struggling with. I am trying to get OAuth app authorization working in C# code via authorization code flow. JWT app is quite simple and easy. I got it easily working. I got the authorization code but failed to get access token. POST url is like this. https://zoom.us/oauth/token?code={authorizationCode}&grant_type=authorization_code&redirect_uri=https://zoom.us
The redirect_uri is same as what’s registered with my app and white listed also. In the Authorization header I give “Bearer Base64(Client_Id:Client_Secret)” . For base64 encoding, I have used https://www.base64encode.org/, character set is UTF8, destination new line separator LF (Unix). I am on Windows 10. I don’t think LF (Unix) cause problem here. I get exact same error as OP. It’s not working in C# code and from postman also.
i havent, will try it real quick, and get back to you
thanks
UPDATE: thanks for the hints, i think i manage to make this work, as it turns out that i need to put the query params as part of the 3rd argument on axios
Hello Tommy,
I’m using post man for this, and I have also tried this on our application but got same error.
Error : {
“reason”: “Invalid client_id or client_secret”,
“error”: “invalid_client”
}
I have done all the below mention steps.
Step 1:Got the code=obBEe8ewaL_KdyNjniT4KPd8ffDWt9fGB in query parameter.
Step 2: POST request on [zoombaseUrl]/oauth/token?code=0TSK33beUP_n7fue5iHRaOv6Crm_BlGGg&grant_type=authorization_code&redirect_uri=https://oauth.pstmn.io/v1/callback
WITH HEADERS
Authorization:"Basic " ,
Content-Type:“application/x-www-form-urlencoded”
To generate Authorization value I have followed all the steps mention (https://marketplace.zoom.us/docs/guides/auth/oauth) here I have included : between clientId and ClientSecret and then I have encoded them together with :,using base64encode.org/,
I have tried all the solutions mention on these page, please let me know what may be other possible reason for this problem.
Have you double checked that the Client ID and Client Secret in your Authorization header matches that of your OAuth App? Additionally, if your app has both production and development credentials, make sure you’re specifying the same credentials as the instance of the app you authorized.
We have double check the Client ID and Client secret. We have follow all the steps in document. Try all the possible way.
Currently we have only with development.
Can you please share the full details of your request with us by opening up a request here (select the ‘developer’ product from the dropdown, after choosing Technical Support). Share the Client ID/Secret of your app, the Authorization header you’re passing, and the full request URL.