# CORS/JSONp Problems - despite valid key... same errors in Zoom's API playground **URL:** \ **Category:** API and Webhooks\ **Created:** [December 13, 2017, 11:44pm UTC](https://devforum.zoom.us/t/cors-jsonp-problems-despite-valid-key-same-errors-in-zooms-api-playground/822 "2017-12-13T23:44:11Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Aptible\_Team](https://avatars.discourse-cdn.com/v4/letter/a/b4bc9f/32.png) [@Aptible\_Team](https://devforum.zoom.us/u/Aptible_Team)\ **Post date:** [December 13, 2017, 11:44pm UTC](https://devforum.zoom.us/t/cors-jsonp-problems-despite-valid-key-same-errors-in-zooms-api-playground/822/1 "2017-12-13T23:44:11Z")
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: [https://developer.zoom.us/playground/#/Webinars/webinar](https://developer.zoom.us/playground/#/Webinars/webinar) ---
**Author:** ![Joshua\_Woodward1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/joshua_woodward1/32/1480_2.png) [@Joshua\_Woodward1](https://devforum.zoom.us/u/Joshua_Woodward1)\ **Post date:** [December 13, 2017, 11:48pm UTC](https://devforum.zoom.us/t/cors-jsonp-problems-despite-valid-key-same-errors-in-zooms-api-playground/822/2 "2017-12-13T23:48:57Z")
[https://zoom.github.io/api/](https://zoom.github.io/api/)   “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.” ---
**Author:** ![Aptible\_Team](https://avatars.discourse-cdn.com/v4/letter/a/b4bc9f/32.png) [@Aptible\_Team](https://devforum.zoom.us/u/Aptible_Team)\ **Post date:** [December 14, 2017, 12:20am UTC](https://devforum.zoom.us/t/cors-jsonp-problems-despite-valid-key-same-errors-in-zooms-api-playground/822/3 "2017-12-14T00:20:59Z")
Thank you ---
**Author:** ![Aptible\_Team](https://avatars.discourse-cdn.com/v4/letter/a/b4bc9f/32.png) [@Aptible\_Team](https://devforum.zoom.us/u/Aptible_Team)\ **Post date:** [December 14, 2017, 12:32am UTC](https://devforum.zoom.us/t/cors-jsonp-problems-despite-valid-key-same-errors-in-zooms-api-playground/822/4 "2017-12-14T00:32:39Z")
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? ---
**Author:** ![Joshua\_Woodward1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/joshua_woodward1/32/1480_2.png) [@Joshua\_Woodward1](https://devforum.zoom.us/u/Joshua_Woodward1)\ **Post date:** [December 14, 2017, 12:37am UTC](https://devforum.zoom.us/t/cors-jsonp-problems-despite-valid-key-same-errors-in-zooms-api-playground/822/5 "2017-12-14T00:37:57Z")
HI, Neither v1 or v2 supported CORS   The playground because it is part of \*.zoom.us 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 [https://developer.zoom.us/blog/using-zoom-apis-version-2-with-postman/](https://developer.zoom.us/blog/using-zoom-apis-version-2-with-postman/) (and v1 [https://developer.zoom.us/blog/using-zoom-apis-with-postman/](https://developer.zoom.us/blog/using-zoom-apis-with-postman/)) ---
**Author:** ![DeveloperBot](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/developerbot/32/12632_2.png) [@DeveloperBot](https://devforum.zoom.us/u/DeveloperBot)\ **Post date:** [August 21, 2020, 5:22pm UTC](https://devforum.zoom.us/t/cors-jsonp-problems-despite-valid-key-same-errors-in-zooms-api-playground/822/6 "2020-08-21T17:22:19Z")