CORS/JSONp Problems - despite valid key... same errors in Zoom's API playground


I am attempting to get a webinar (to display date/time) and register webinar participants from our website. However, it appears that v2 updates have disabled a jsonp response. My token is good. I get correct JSON back when I ask for jsonp, but otherwise get CORS errors: No 'Access-Control-Allow-Origin' header is present… 403 response.

I get the same response when trying to access a valid webinar by id Zoom’s API playground:



“Our API is a server side implementation designed around REST, it does not support cross-origin resource sharing or access via a client side web application.”


Thank you


I appreciate the prompt response. I’ll weigh the benefits of an app to proxy a get and post to support our use case. 

Did the API used to support a client side web application? Is that how the API playground used to work?



Neither v1 or v2 supported CORS


The playground because it is part of * is whitelisted. Currently there is a known issue where some endpoints show a CORS issue, however that is because it fails elsewhere, a fix is coming very soon for that.


I strongly recommend a REST tool for testing versus the playground. There is a blog post on how to use Postman (and v1