403 Forbidden on Zoom REST API v1

All requests to REST API v1is returning 403 Forbidden


403 Forbidden

403 Forbidden


Which App Type (OAuth / Chatbot / JWT / Webhook)?

Which Endpoint/s?

How To Reproduce (If applicable)
Steps to reproduce the behavior:

  1. Send a request to this endpoint https://api.zoom.us/v1/user/list with api_key and api_secret you will get the exception.

Screenshots (If applicable)

Additional context

Hi @zoom16,

Our developer team send out numerous communications to all developers that our v1 APIs will be disabled by May 31st.

Here is a blog highlighting how to migrate from v1 to v2 APIs[1]. Here is our Marketplace developer documentation[2] to get your JWT credentials via JWT app and v2 API reference page[3].

1 - https://medium.com/zoom-developer-blog/your-guide-to-migrating-from-v1-to-v2-apis-d4ded0474c04
2 - https://marketplace.zoom.us/docs/guides/build/jwt-app
3 - https://marketplace.zoom.us/docs/api-reference/introduction

Let us know if this helps.

It worked with API V2. Thanks :slight_smile:

Hello , Can you share me , how did you make workable in v2 (postman if possible)

Hi @bishnuateet,

Please refer to the link below for our V2 API Postman guides on how to import our API into postman - https://marketplace.zoom.us/docs/guides/guides/postman#zoom-api

Let us know if this helps.


Dear @Michael_Purnell
I am trying to create meeting for my online class thru api earlier (3 days ago) it was working fine in v1 but now it’s not working anymore and try to modify in v2 froma guidelines you wrote in medium, i couldn’t get any response in postman too, Can you show me an example of creating meeting in postman if possible ??

Hi @bishnuateet

For API v2, we need to do the authorization using oauth2 or JWT to get a token that will be sent in the header of all the requests.
I have my meeting creation & other stuffs in the backend.
The easiest and quick way I took to migrate from v1 to v2 was by using JWT.
Before you call any API v2 endpoint you’ll have to generate the JWT token. (You can reuse the token if you are calling multiple endpoints one after the other. And for security reasons keep the expiry time in your JWT token less than a minute).
This way you should be able to use the API v2 without any issues.
Have a nice day :slight_smile:

Thanks for your advice @zoom16!

@bishnuateet, use our API Reference for an example request body: