Invalid api key or secret using postman/insomnia

API and Webhooks
1

Hello,
I request a Bearer Token using the following post request via postman or insomnia

https://zoom.us/oauth/token?grant_type=client_credentials&client_id={myclientid}&client_secret={myclientsecert}

response:
{
“access_token”: “xxx”,
“token_type”: “bearer”,
“expires_in”: 3599,
“scope”: “group:read:admin group:write:admin imgroup:read:admin imgroup:write:admin user:read:admin user:write:admin”
}

Then I set up a get request via postman or insomnia
https://api.zoom.us/v2/users
using Bearer as Authentication type using the token I requested before.

Response of the get request is
{
“code”: 200,
“message”: “Invalid api key or secret.”
}

The scope is user:read:admin so I should have access to the Users List API using this grant type token or not??

Thanks in advance,
Britta

Insomnia Timeline Output

GET /v2/users HTTP/1.1
Host: api.zoom.us
User-Agent: insomnia/7.0.1
Cookie: cred=xxx; _zm_currency=EUR; _zm_mtk_guid=xxx; _zm_o2nd=xxx; _zm_o2trackid={client_id}; _zm_page_auth=xxx; _zm_ssid=xxx> Content-Type: application/json;charset=UTF-8
Authorization: Bearer {token}
Accept: /
Content-Length: 1

| =

  • upload completely sent off: 1 out of 1 bytes

< HTTP/1.1 400 Bad Request
< Date: Thu, 07 Nov 2019 15:08:21 GMT
< Content-Type: application/json;charset=UTF-8
< Transfer-Encoding: chunked
< Connection: keep-alive
< Server: ZOOM
< x-zm-trackingid: WEB_xxx

  • Received 62 B chunk
  • Connection #73 to host api.zoom.us left intact
2

Hey @britta,

It seems like you are using the Zoom Chatbot authentication flow instead of the OAuth flow.

Per our docs, in order to call the GET /users endpoint, you must either use a JWT Token, or an OAuth access_token.

Let me know if you need additional guidance! :slight_smile:

Thanks,
Tommy