Skip to content
Telephony/CPaaS

callfire.com

CallFire API Documentation sandbox and mock API

CallFire Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
122
Collections
-
Event types
-
Start this simulation
example request
curl https://your-callfire.slurry.io/v2/calls \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version V2.

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 122.

  • GET/calls
  • POST/calls
  • GET/calls/broadcasts
  • POST/calls/broadcasts
  • GET/calls/broadcasts/{id}
  • PUT/calls/broadcasts/{id}
  • POST/calls/broadcasts/{id}/archive
  • GET/calls/broadcasts/{id}/batches
  • POST/calls/broadcasts/{id}/batches
  • GET/calls/broadcasts/{id}/calls
  • POST/calls/broadcasts/{id}/recipients
  • POST/calls/broadcasts/{id}/start
CallFire API Documentation sandbox and mock API | Slurry