Skip to content
Other

tvmaze.com

TVmaze user sandbox and mock API

Access to the user API is only possible for users with a [premium](http://www.tvmaze.com/premium) account. A user can only access their own user data. Authentication uses HTTP Basic. Use the TVmaze username as authentication username, and the TVmaze API key as authentication password. Your API key can be found on your [dashboard](http://www.tvmaze.com/dashboard). To try out these API calls from th Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
42
Collections
-
Event types
-
Start this simulation
example request
curl https://your-tvmaze.slurry.io/v1/auth/validate \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 1.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 42.

  • POST/auth/poll
  • POST/auth/start
  • GET/auth/validate
  • POST/scrobble/episodes
  • PUT/scrobble/episodes/{episode_id}
  • POST/scrobble/shows
  • GET/scrobble/shows/{show_id}
  • GET/user/episodes
  • GET/user/episodes/{episode_id}
  • PUT/user/episodes/{episode_id}
  • DELETE/user/episodes/{episode_id}
  • GET/user/follows/networks