imsclf
(Ian)
September 7, 2023, 3:57pm
1
https://zoom.us/oauth/token?grant_type=account_credentials&accountid={accountId}
I am trying to generate an access token for a server to server oauth application that I am migrating from JWT and am getting the error:
{“reason”: “Invalid client_id or client_secret”, “error”: “invalid_client”}.
I’ve double checked that the account id, client id, and client secret match what is shown in the application configuration, and that the app has been activated.
My curl command looks like this:
curl --location ‘https://zoom.us/oauth/token?grant_type=account_credentials&accountId={accountId} ’
–header ‘Authorization: Basic {token}’
The token is my base64 encoded clientId:clientSecret and looks like (this is not the actual value):
VGhpcyBpcyBhIHRlc3Qgc3RyaW5nLg==
gianni.zoom
(OOO 11/1 - 11/8)
September 7, 2023, 4:47pm
3
Hi @imsclf ,
Can you please try with our postman workspace? Postman
I know this is not the actual value, but it seems to be too short, hmm.
imsclf
(Ian)
September 7, 2023, 5:46pm
4
@gianni.zoom
Yes, I get the same error using your Postman Workspace. I’m not able to post an image, but here’s the cURL code snippet that Postman generated:
curl --location ‘https://zoom.us/oauth/token?grant_type=account_credentials&accountid={accountid} ’ \
–header ‘Content-Type: application/x-www-form-urlencoded’ \
–header ‘Authorization: Basic {token}’ \
–header ‘Cookie: {cookie}’
My actual token I referenced in my initial post is 76 characters - yes my example was shorter.
gianni.zoom
(OOO 11/1 - 11/8)
September 11, 2023, 9:10pm
5
Hi @imsclf
Can you please share a screen recording of your workflow in our private message? Thanks!
gianni.zoom
(OOO 11/1 - 11/8)
September 11, 2023, 9:17pm
6
Developer was able to resolve issue. Client id/client secret was changing with copy/paste.