Skip to content
Other

art19.com

ART19 Content API Documentation sandbox and mock API

The ART19 Content API conforms to the [JSON:API specification](http://jsonapi.org). API requests **MUST** use the HTTP Accept header: `Accept: application/vnd.api+json` API requests **MUST** be authenticated using the HTTP Authorization header: `Authorization: Token token="your-token", credential="your-credential"` ## General Notes Some query parameters use unencoded [ and ] characters simply for Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
22
Collections
-
Event types
-
Start this simulation
example request
curl https://your-art19.slurry.io/classification_inclusions \
  -H "Authorization: Bearer slurry_sim_..."

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

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

  • GET/classification_inclusions
  • GET/classification_inclusions/{id}
  • GET/classifications
  • GET/classifications/{id}
  • GET/credits
  • GET/credits/{id}
  • GET/episodes
  • GET/episodes/{id}
  • GET/episodes/{id}/next_sibling
  • GET/episodes/{id}/previous_sibling
  • GET/images
  • GET/images/{id}