Hello there,

I’ve been trying to use the Zoom API to get a listing of webinars to display on a custom web page, however I keep getting a CORS origin error: Access to XMLHttpRequest at '' from origin 'https://myurlhere' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.

I’ve seen somewhere in your docs that I have to use the Web SDK. I will appreciate it if there are clear directives/instructions on how to achieve this.


1 Like

You’re correct that you can use the Zoom Web Client SDK to overcome these limitations, but you’ll be aware that behind the scenes, this is using Web Assembly: (please pay special attention to the LIMITATIONS section of the docs)

There are only one of three ways to resolve CORS issues:

  1. Proxy the requests from Client->Your Server (removes browser/sandbox restrictions, best practice…most in control of developers)
  2. Use Web Assembly or Web Workers (but these can still have limitations that need exploring)
  3. If the server accepts your domain or wildcard domains (not recommended since it is introduces security risks, and will never be supported by Zoom’s APIs)

Personally, unless your use-case requirements insist on having client-side code perform these Zoom API requests, I would recommend proxying them through your backend services. This has an added benefit of limiting security risks while also working well with elastic architectures to address scale without impacting client-side usability.

1 Like

is there any hack to call zoom api from jquery now ?

WIsh there was anyway a it could be called from xhr without all these webassembly & stuffs

Hey @ofd.aws96,

You can setup a simply Node.js server to call the API:


1 Like

Hi i read on other cors error post, that i need to do a request from a server side, its actually more relevant if i post a reply there on that post but unfortunately its been closed that i cant post any reply, so i decided to ask it here instead

what about refreshing a token, should it also be a server side request? or can i do it from the client? as i can do a token request from client side


Hey @littlechad,

Good question. For all of our API endpoints, your requests should be executed server side. You will run into errors (CORS) if you try to submit requests from your client side.

Let me know if this helps to clarify,

1 Like