Hello everyone,

I am using the Zoom API in my React.js application to create meetings for users to join.
I have set up a Server-to-Server (Internal) App through the Zoom Marketplace, which allows me to create meetings programmatically. Here is a detailed description of my setup and the issue I am facing:

• Objective: My goal is to create multiple Zoom meetings using a single Zoom account, where participants can join, but the host account never joins the meetings. The account is solely used for scheduling/creating the meetings.
• Challenge: I understand that Zoom imposes a limitation where a single account cannot host more than one meeting at the same time. However, since the host (the account creating the meetings) never joins, I would like clarification on whether it’s possible to create and manage multiple meetings simultaneously using this account without encountering any issues.
• Technical Details:
  • I have enabled the Join Before Host option when creating meetings (join_before_host: true).
  • The meetings are created through API calls, and the users are provided with the join links to participate in the meetings.
  • We need to create multiple meetings that may overlap in time, but again, the host will not be joining.

Could you confirm if this setup allows me to create multiple meetings concurrently, given that the host will not be attending? If there are any best practices or limitations I should be aware of, please let me know.

Thank you for your assistance.

Hi everybody,

Has anyone tried using Zoom's YouTube app from the Marketplace?  We're hoping to use it to substitute the need for hosts to share their screen to show YouTube content.  However, we notice a few issues:
--The host can hear the YouTube audio, but guests can't, despite the video being in sync.
--When trying to change from one video to another, the app performs inconsistently: it either changes to the next video, or nothing happens.  Even when the current video ends, and you attempt to select a different one, it doesn't play, requiring you to close out of the app and reopen it.

Just curious to see if anyone has identified other bugs so I can reference those issues as I open a case with Zoom support.  Thanks!

--Andy Borts, Zoom Administrator, UNLV

Hi Zoom Developer Community,

I’m currently in the process of submitting my app for Beta Testing on the Zoom Marketplace.
After completing all mandatory requirements and switching the environment to Production, my app failed the Security and Privacy Compliance Review with the following message:

“We noticed your app supports TLS 1.0 & TLS 1.1, which are considered insecure. Please consider ceasing/upgrading these versions.”

However, I’ve verified multiple times that:

• TLS 1.0 and 1.1 are completely disabled on our servers.

• Only TLS 1.2 and 1.3 are enabled for all inbound and outbound HTTPS traffic.

• The backend (Node.js / NestJS) runs behind a reverse proxy with strict SSL configuration.

We’ve attached full configuration and connection test screenshots in our reply to the Marketplace team as proof, but the review still failed.

I’d really appreciate if anyone from the Zoom team or community could help clarify:

1. How does Zoom test or verify TLS protocol versions during app security review?

2. Could there be any specific endpoint or redirect Zoom checks that might cause this false flag?

3. Has anyone else encountered this issue during Beta or Production app review, and how did you resolve it?

We’ve been waiting quite a while for this process, so any insight or escalation would mean a lot.
Thanks in advance for your support and time!

Best,

Hello Zoom Developer Support,

I’m using a Server-to-Server OAuth app to retrieve past webinar participant data across all users in our Business account.
The app authenticates successfully and can list all users, but any attempt to call /report/webinars or /report/history_meetings returns an error — even though these webinars clearly exist in the Zoom web portal under “Reports → Webinar Attendance”.

Endpoints Tested