Skip to content
Telephony/CPaaS

zoom.us

Zoom sandbox and mock API

The Zoom API allows developers to access information from Zoom. You can use this API to build private services or public applications on the [Zoom App Marketplace](http://marketplace.zoom.us). To learn how to get your credentials and create private/public applications, read our [Authorization Guide](https://marketplace.zoom.us/docs/guides/authorization/credentials). All endpoints are available via Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
373
Collections
-
Event types
-
Start this simulation
example request
curl https://your-zoom-us.slurry.io/v2/accounts \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API 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 373.

  • GET/accounts
  • POST/accounts
  • GET/accounts/{accountId}
  • DELETE/accounts/{accountId}
  • GET/accounts/{accountId}/billing
  • PATCH/accounts/{accountId}/billing
  • GET/accounts/{accountId}/billing/invoices
  • GET/accounts/{accountId}/billing/invoices/{invoiceId}
  • GET/accounts/{accountId}/lock_settings
  • PATCH/accounts/{accountId}/lock_settings
  • GET/accounts/{accountId}/managed_domains
  • PATCH/accounts/{accountId}/options