Skip to content
Meeting recording & transcripts

grain.com

Test against the Grain API

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

Operations
13
Start this simulation Vendor documentation
example request
curl https://your-grain.slurry.io/_/public-api/v2/token-info \
  -H "Authorization: Bearer slurry_sim_live_..."

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

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.

  • POST/_/public-api/v2/recordings
  • POST/_/public-api/v2/recordings/{recording_id}
  • PATCH/_/public-api/v2/recordings/{recording_id}
  • GET/_/public-api/v2/recordings/{recording_id}/transcript
  • GET/_/public-api/v2/recordings/{recording_id}/transcript.vtt
  • GET/_/public-api/v2/recordings/{recording_id}/transcript.txt
  • POST/_/public-api/v2/teams
  • POST/_/public-api/v2/meeting_types
  • POST/_/public-api/v2/users
  • POST/_/public-api/v2/hooks
  • POST/_/public-api/v2/hooks/create
  • DELETE/_/public-api/v2/hooks/{hook_id}

Does this simulation differ from the real Grain 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