Skip to content
Other

clarify.io

api.clarify.io sandbox and mock API

The API to Search and Understand Audio & Video Data. Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
21
Collections
-
Event types
-
example request
curl https://your-clarify.slurry.io/v1/bundles \
  -H "Authorization: Bearer slurry_sim_..."

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

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

  • GET/v1/bundles
  • POST/v1/bundles
  • GET/v1/bundles/{bundle_id}
  • PUT/v1/bundles/{bundle_id}
  • DELETE/v1/bundles/{bundle_id}
  • GET/v1/bundles/{bundle_id}/insights
  • POST/v1/bundles/{bundle_id}/insights
  • GET/v1/bundles/{bundle_id}/insights/{insight_id}
  • GET/v1/bundles/{bundle_id}/metadata
  • PUT/v1/bundles/{bundle_id}/metadata
  • DELETE/v1/bundles/{bundle_id}/metadata
  • GET/v1/bundles/{bundle_id}/tracks