Skip to content
Meeting recording & transcripts

recall.ai

Test against the Recall.ai API

A hosted, stateful simulation shaped like the Recall.ai API. Writes persist, data moves on a schedule and every change can fire a signed webhook. Unofficial: not affiliated with recall.ai.

Operations
13
Start this simulation Vendor documentation
example request
curl https://your-recall-ai.slurry.io/api/v1/bot/ \
  -H "Authorization: Bearer slurry_sim_live_..."

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

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

  • GET/api/v1/bot/
  • POST/api/v1/bot/
  • GET/api/v1/bot/{id}/
  • PATCH/api/v1/bot/{id}/
  • DELETE/api/v1/bot/{id}/
  • POST/api/v1/bot/{id}/leave_call/
  • GET/api/v1/recording/
  • GET/api/v1/recording/{id}/
  • POST/api/v1/recording/{id}/create_transcript/
  • GET/api/v1/transcript/
  • GET/api/v1/transcript/{id}/
  • DELETE/api/v1/transcript/{id}/

Does this simulation differ from the real Recall.ai 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