Skip to content
Meeting recording & transcripts

zoom.us

Test against the Zoom Meetings & Cloud Recordings API

A hosted, stateful simulation shaped like the Zoom Meetings & Cloud Recordings API. Writes persist, data moves on a schedule and every change can fire a signed webhook. Unofficial: not affiliated with zoom.us.

Operations
16
Start this simulation Vendor documentation
example request
curl https://your-zoom-meetings.slurry.io/v2/meetings/123 \
  -H "Authorization: Bearer slurry_sim_live_..."

Your simulation gets its own hostname, key and IP allow-list. Spec snapshot: version 2.0.0.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 16.

  • GET/meetings/{meetingId}
  • PATCH/meetings/{meetingId}
  • DELETE/meetings/{meetingId}
  • GET/meetings/{meetingId}/recordings
  • DELETE/meetings/{meetingId}/recordings
  • GET/meetings/{meetingId}/registrants
  • POST/meetings/{meetingId}/registrants
  • PUT/meetings/{meetingId}/status
  • GET/past_meetings/{meetingUUID}
  • GET/past_meetings/{meetingUUID}/participants
  • GET/users/{userId}
  • PATCH/users/{userId}

Does this simulation differ from the real Zoom Meetings & Cloud Recordings API?

Tell us about wrong response shapes, status codes, missing endpoints or unrealistic data. If you have a simulation of it, report from its Issues tab so we can see the exact call.

Sign in to report an issue