Skip to content
Other

zeno.fm

Aggregators API Service sandbox and mock API

Aggregators API Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
18
Collections
-
Event types
-
Start this simulation
example request
curl https://your-zeno-fm.slurry.io/api/v2/podcasts/categories \
  -H "Authorization: Bearer slurry_sim_..."

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

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

  • GET/api/v2/podcasts/categories
  • GET/api/v2/podcasts/countries
  • POST/api/v2/podcasts/create
  • GET/api/v2/podcasts/languages
  • POST/api/v2/podcasts/search
  • GET/api/v2/podcasts/{podcastKey}
  • PUT/api/v2/podcasts/{podcastKey}
  • DELETE/api/v2/podcasts/{podcastKey}
  • GET/api/v2/podcasts/{podcastKey}/episodes
  • POST/api/v2/podcasts/{podcastKey}/episodes/create
  • GET/api/v2/podcasts/{podcastKey}/episodes/{episodeKey}
  • PUT/api/v2/podcasts/{podcastKey}/episodes/{episodeKey}