I’m having an issue generating an access token to set up a Zoom API calls for server-to-server Oauth.
I’ve followed all instructions I can find, and I’m using my client_id, client_secret, and account_id as directed.
The error I usually receive is: Status code 400
{“reason”:“Invalid client_id or client_secret”,“error”:“invalid_client”}
I’ve checked my zoom client_id and client_secret, and they are correct. I have entered them separated by a “:”, as directed by Server-to-Server OAuth
Can anyone tell me what I’m doing wrong here?
Do I need to enter values in the “Username” and “Password” fields?
Or should I be using a different type of authentication?
Move the request access token to the auth part (token endpoint (post) is the url you actually have in request access token call, set authozation header in the Token call headers section. Put your request data into the body JSON like grant_type=account_credentials&account_id=youraccountID
Delete the token call at the bottom, and test with a simple call like get account info
I read through several threads/blogs that I’ve now lost the links for… but here’s what my solution looked like. Username was the client ID and password was the client secret.
I hope this helps! I am very much the person for whom no-code app builders exist, so I could not explain why this works if I tried.
I don’t recommend using this with account credentials because your access token will be available on client side too. So your user could use it and access to anything this account have access. Better to use custom oauth2
Hey guys, thank you SO MUCH for the quick responses! I’ve been able to make both solutions work! Privacy-wise, it’s not big deal for us since we’ll be using it internally for operations analysis.