Skip to content
Other

setlist.fm

setlist.fm sandbox and mock API

<p> The setlist.fm API has been designed to give you easy access to setlist data in order to build fancy websites and other applications. Before starting to use the API, be sure to ... <ol> <li>... understand how setlist.fm works (the <a href="https://www.setlist.fm/faq">FAQ</a> and the <a href="https://www.setlist.fm/guidelines">Guidelines</a> are a good starting point),</li> <li>... read this do Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
15
Collections
-
Event types
-
Start this simulation
example request
curl https://your-setlist-fm.slurry.io/rest/1.0/search/artists \
  -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 15.

  • GET/1.0/artist/{mbid}
  • GET/1.0/artist/{mbid}/setlists
  • GET/1.0/city/{geoId}
  • GET/1.0/search/artists
  • GET/1.0/search/cities
  • GET/1.0/search/countries
  • GET/1.0/search/setlists
  • GET/1.0/search/venues
  • GET/1.0/setlist/version/{versionId}
  • GET/1.0/setlist/{setlistId}
  • GET/1.0/user/{userId}
  • GET/1.0/user/{userId}/attended