tldv.io

Test against the tl;dv API

A hosted, stateful simulation shaped like the tl;dv API. Writes persist, data moves on a schedule and every change can fire a signed webhook. Unofficial: not affiliated with tldv.io.

Operations: 12

Start this simulation Vendor documentation

example request

curl https://your-tldv.slurry.io/v1alpha1/health \
  -H "Authorization: Bearer slurry_sim_live_..."

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

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

All 12.

POST/v1alpha1/meetings/import
GET/v1alpha1/meetings/{meetingId}/transcript
GET/v1alpha1/meetings/{meetingId}/notes
GET/v1alpha1/meetings
GET/v1alpha1/meetings/{meetingId}
GET/v1alpha1/meetings/{meetingId}/highlights
GET/v1alpha1/meetings/{meetingId}/download
GET/v1alpha1/health
POST/v1alpha1/meetings/upload
GET/v1alpha1/meetings/upload/{uploadId}
DELETE/v1alpha1/meetings/upload/{uploadId}
POST/v1alpha1/meetings/upload/{uploadId}/complete

Does this simulation differ from the real tl;dv 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.