Meeting recording & transcripts
googleapis.com
Test against the Google Meet REST API
A hosted, stateful simulation shaped like the Google Meet REST API. Writes persist, data moves on a schedule and every change can fire a signed webhook. Unofficial: not affiliated with googleapis.com.
- Operations
- 13
example request
curl https://your-google-meet.slurry.io/v2/conferenceRecords \
-H "Authorization: Bearer slurry_sim_live_..."Your simulation gets its own hostname, key and IP allow-list. Spec snapshot: 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 13.
- GET/v2/conferenceRecords
- GET/v2/conferenceRecords/{conferenceRecordsId}
- GET/v2/conferenceRecords/{conferenceRecordsId}/recordings
- GET/v2/conferenceRecords/{conferenceRecordsId}/recordings/{recordingsId}
- GET/v2/conferenceRecords/{conferenceRecordsId}/participants/{participantsId}
- GET/v2/conferenceRecords/{conferenceRecordsId}/participants
- GET/v2/conferenceRecords/{conferenceRecordsId}/transcripts
- GET/v2/conferenceRecords/{conferenceRecordsId}/transcripts/{transcriptsId}
- GET/v2/conferenceRecords/{conferenceRecordsId}/transcripts/{transcriptsId}/entries/{entriesId}
- GET/v2/conferenceRecords/{conferenceRecordsId}/transcripts/{transcriptsId}/entries
- POST/v2/spaces
- GET/v2/spaces/{spacesId}
Does this simulation differ from the real Google Meet REST 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.