API Endpoint(s) and/or Zoom API Event(s)
This is for an app that calls RTMS stop and start to capture audio
Description
I’ve asked Claude.ai and it suggests this as a possible way to load test an RTMS surface app. (We have found that the owner of the meeting has to have a business account to use RTMS)
Is this correct?
=========================
If you specifically need to validate the full pipeline — real Zoom meetings, real audio/video, real RTMS delivery — the supported path is the Zoom Meeting SDK (there’s a headless/Linux variant meant for exactly this kind of bot use case), not trying to script actual desktop/mobile Zoom clients. With it you can:
- Programmatically create meetings via the Zoom API (needs a Business/Enterprise account with enough concurrent meeting capacity and licenses).
- Spin up SDK-based “participant” processes that join those meetings and can inject synthetic audio/video streams.
- Have RTMS enabled on those meetings so your app receives real streamed data.
Caveats worth knowing before you build this:
- You need enough licensed hosts/concurrent meeting capacity for real load (this gets expensive fast).
- Zoom’s ToS generally prohibits unauthorized automation of the actual client apps (driving the desktop/mobile UI via scripting) — the Meeting SDK is the sanctioned way to get bot participants, not automating the regular client.
- At meaningful scale (dozens+ of simultaneous meetings/bots), you should expect to hit rate limits or anti-abuse triggers, so it’s worth reaching out to Zoom developer support ahead of time to flag that you’re load testing and ask about any accommodations — some platforms offer sandboxes or elevated quotas for exactly this.
**========================================
Is there a better way to test are application under load to validate that it can scale?
**