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: https://marketplace.zoom.us/docs/guides/zoom-sdks/Web-Client-SDK (please pay special attention to the LIMITATIONS section of the docs)
There are only one of three ways to resolve CORS issues:
- Proxy the requests from Client->Your Server (removes browser/sandbox restrictions, best practice…most in control of developers)
- Use Web Assembly or Web Workers (but these can still have limitations that need exploring)
- 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.