Every setlist.fm concert, song by song, as JSON
- endpoints
- 16
- credits per call
- 1–3
setlist.fm is the largest wiki of concert setlists.
/setlistfm/v1
- POST/setlistfm/v1/search1 credit
- POST/setlistfm/v1/setlist1 credit
- POST/setlistfm/v1/artist2 credits
- POST/setlistfm/v1/artist_stats2 credits
- POST/setlistfm/v1/song_stats2 credits
- POST/setlistfm/v1/average_setlist2 credits
- POST/setlistfm/v1/search_artists1 credit
- POST/setlistfm/v1/search_venues1 credit
- POST/setlistfm/v1/city1 credit
- POST/setlistfm/v1/venue1 credit
1 credit per call≈ $1/1,000 calls1,000 free credits, no card
Get a free API keyRun the call yourself, on the real endpoint
Change a parameter and press Try it. The response on the right is what your code will receive.
setlist.fm API
5 of 16 endpoints, ready to run
Search setlists with setlist.fm's own filters
// Press "Try it" and this pane shows exactly what the // live site returned this second — including an empty // result, if that is the truth. No key, no account.
What setlist.fm endpoints does ReefAPI ship?
16 live read endpoints. Read-only data API: no writes, no account actions, no dashboard access on the target site.
search
1 crSearch setlist.fm's setlists with the site's own search.
- required
- —
- optional
- —
setlist
1 crOne setlist in full.
- required
- setlist
- optional
- —
artist
2 crAn artist's page.
- required
- artist
- optional
- —
artist_stats
2 crAn artist's statistics, as the site's stats tabs print them.
- required
- artist
- optional
- —
song_stats
2 crOne song of an artist.
- required
- artist
- optional
- —
average_setlist
2 crThe site's 'average setlist' of an artist for one year or one tour.
- required
- artist
- optional
- —
search_artists
1 crFind artists by name with setlist.fm's own search.
- required
- query
- optional
- —
search_venues
1 crFind venues with setlist.fm's own search.
- required
- query
- optional
- —
city
1 crA city page.
- required
- city
- optional
- —
venue
1 crA venue.
- required
- venue
- optional
- —
festival
1 crA festival series (e.g.
- required
- festival
- optional
- —
festival_edition
3 crOne festival edition (e.g.
- required
- edition
- optional
- —
user
1 crA setlist.fm user's public profile.
- required
- username
- optional
- —
top
1 crsetlist.fm's own charts.
- required
- —
- optional
- —
browse
1 crThe site's alphabetical directory of artists, venues or festivals.
- required
- letter
- optional
- —
autocomplete
1 crThe suggestions setlist.fm's search box shows while typing (artist, venue, city, tour names a…
- required
- query
- optional
- —
Every parameter, every allowed value →
Missing a setlist.fm endpoint, or need a source we don't have yet?Contact us real people · same-day reply.How the setlist.fm API works
setlist.fm is a normal ReefAPI surface — the same four rules that hold for every other engine on the key.
No OAuth app, no request signing, no per-site account. One key covers all 694 engines.
Every route is a POST with a JSON body. Parameters are validated against the published schema before anything is charged.
Credits, not seats. Failed and blocked calls are never charged, and nothing is cached: every call reads the source live.
One envelope everywhere. meta carries latency_ms, record_count and the endpoint that answered.
From an artist to a tour's typical setlist
Find the artist, list a tour's concerts, open one, then compare it with the tour's average.
Artists matching the text with their setlist.fm ids and setlist counts (Muse: 53d6ebd5, 1,729 setlists).
The tour's setlists, 10 per page with the site's total (33 for The Wow! Signal).
One concert: 27 songs in order with tape songs, covers, notes, the encore and set times.
The tour's typical running order, encore included.
A tour's concerts, a full setlist and the setlist fans can expect.
curl -X POST https://api.reefapi.com/setlistfm/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"query":"coldplay"}'{
"ok": true,
"data": { … },
"meta": {
"api": "setlistfm",
"endpoint": "search",
"mode": "live",
"latency_ms": …,
"record_count": …
},
"error": null
}What a setlist.fm field actually contains
Fields that read differently from how they look. Every row was measured against live setlist.fm on 2026-11-19.
| Field | What it holds |
|---|---|
| sets[].songs[].position / set_position | position counts every song of the concert in page order (tape songs included); set_position restarts in each set. The Muse setlist 33754819 has 27 positions: 25 songs played live and 2 from tape. |
| tape | true when the page marks the song "played from tape" (intros and outros). song_count counts the songs without it, tape_count the songs with it. |
| cover / original_artist / with[] | cover = the artist whose song was covered ("Danny Dill cover"); original_artist = the author named next to a tape song or a related-artist song ("CHVRCHES song"); with[] = the guest artists the page links ("with Jake Renick Simpson"). A "with ..." note that names no artist page stays in info. |
| info | The song's note as the page prints it ("extended intro", "Solo"), several notes joined with "; ". |
| sets[].name / encore | The set heading the page prints ("Encore", a named set) and the encore number; songs before any heading are the main set (name null). |
| venue / sub_venue | venue is the venue page the setlist belongs to, with city, state (US, Canada, Australia) and country split from the printed name. sub_venue is the stage or room when the page names one ("Apex Stage" at Donington Park). |
| set_times | doors, scheduled start, start and end as the page prints them ("6:30 PM", the venue's local time), with the tour's average start after doors and average show length when the site has them. Filled on 8 of 10 setlists checked. |
| total (search) | The site's own count: the sum of its year filter. It matched the page count (total / 10, rounded up) on every search checked. Lists stop at page 1,000, so reachable_pages tells how many of the pages can be opened. |
| attendances | How many setlist.fm users marked themselves as having been at the concert (157 for the Muse setlist above). |
| last_editor / last_edit_at / last_updated | The user who last edited the setlist with their site role, the time of that edit, and the setlist's last update time, both in UTC as printed. |
setlist.fm does not publish venue coordinates on its pages, so none are returned; city, state and country are.
setlist.fm coverage, measured
Every number below was read from live setlist.fm on 2026-11-19: 114 calls over 16 actions, 114 answered, plus 16 checks that wrong inputs get the right error.
Every filter changed the count: "coldplay" 1,585 setlists, with Coldplay's artist id 1,488, in the UK 396, in 2016 81, at Wembley Stadium 23. For Muse (1,729): The Wow! Signal tour 33, Supermassive Black Hole 877, all of 2024 2. The editor filter returned 157,836 setlists for one user, 2,963 of them edited between 1 and 19 November 2026.
Search rows equalled the full setlist (date, venue, artist, tour and the first 12 songs in order) on 13 of 13 setlists across 13 artists. Song plays on `song_stats` equalled the song search (877 = 877) and the sum of its plays per year; an artist's setlist total equalled the sum of its years (1,729); a festival's lineup rows equalled the count the page prints (661); a user's attended count equalled the attendee search (197).
On 382 search rows artist, venue, city and country were filled 382 of 382, the tour 247, set times 279 and the song preview 278 (upcoming and empty setlists have none). Across 10 full-setlist calls 195 songs carried a name, 181 a song id (tape songs have none), 15 a cover artist, 17 guest artists and 50 a note.
Three consecutive pages repeated no setlist on two lists ("radiohead" 1,232 and Coldplay's 1,488). Every list is 10 rows per page, the site's own size.
A search stops at page 1,000 (10,000 rows): city Manchester has 76,958 setlists. Artist, venue and country lists of a search show up to 50 names, the rest as one other count. setlist.fm pages show no venue coordinates. A setlist's edit history is not public.
What people build with setlist.fm
The jobs this data is most often used for.
Show the setlist of last night's concert with every song, cover and guest.
Predict a tour's setlist from the average setlist and song statistics.
Track how often and where an artist plays a song.
Build venue and city concert histories with upcoming shows.
endpoints
credits per call
What setlist.fm data costs
The cheapest call here is 1 credit, so $15/mo (Pro) buys 10,000 of them — $1.50 per 1,000 credits. Credits roll over and never expire, and failed or blocked calls are not charged.
- 1,000 free credits on signup, no card
- One key, all 694 APIs, one credit pool
- Failed and blocked calls are never charged
- Credits roll over and never expire
Call it in two lines
Sign up, get 1,000 credits and one key that works on every engine. Then this is the whole protocol.
curl -X POST https://api.reefapi.com/setlistfm/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"query":"coldplay"}'import os
import requests
REEF_KEY = os.environ["REEF_KEY"]
r = requests.post(
"https://api.reefapi.com/setlistfm/v1/search",
headers={"x-api-key": REEF_KEY},
json={
"query": "coldplay"
},
timeout=90,
)
print(r.json()["data"])Have a question? We got answers.
The questions people actually ask before wiring up setlist.fm.
Do I need a setlist.fm API key?▾
No. The data comes from setlist.fm's public pages; you only use your ReefAPI key.
How do I get every setlist of an artist?▾
`artist` takes the artist's name, id or setlist.fm link and returns the artist with 10 setlists per page and the site's filters (tour, country, venue, year): Coldplay in 2024 returned 65 setlists. `search` with the artist id gives the same list with every other filter on top.
Can I find the concerts where a song was played?▾
Yes. `search` with the artist id and the song id returns the setlists containing it: 877 for Muse and Supermassive Black Hole, the same number `song_stats` prints as the song's total plays. `song_name` searches by title across all artists.
What is an average setlist?▾
setlist.fm's typical running order for one year or one tour of an artist. `average_setlist` returns it like a real setlist; Metallica in 2023 has 19 songs. The site has no average across all concerts, so year or tour is required.
Are covers and guest appearances included?▾
Yes, per song: the covered artist, the guests on stage, the author of a tape song and the song note. `artist_stats` with view covers, with and covered sums them up for the whole career.
Can I get festival lineups?▾
`festival` lists a festival's editions (Glastonbury: 41) and `festival_edition` returns one edition's full lineup in one call, with stage, date, scheduled start and attendance per setlist: 661 rows for Glastonbury 2025.
Can I see which concerts a user went to?▾
Yes, for public profiles: `search` with attendee returns the concerts a user marked as attended (197 for FFalex, equal to the count on the profile), and `user` returns the profile itself.
How far back can I page?▾
Ten setlists per page, up to page 1,000 of any one search. A wide search such as city Manchester (76,958 setlists) needs narrower filters (year, date range, venue) to reach its older rows.
What is the setlist.fm API?▾
setlist.fm API is a ReefAPI endpoint group for setlist.fm concert setlists as json: search by artist, venue, city, country, tour, song, date or attendee; every song in order with covers, guests, tape and encores; song, tour and album statistics, average setlists, venues, cities, festivals and user profiles. It returns live JSON through POST requests under /setlistfm/v1.
Is the setlist.fm API free to try?▾
Yes. ReefAPI starts with 1,000 free credits, no card required. setlist.fm calls use the same shared credit balance as every other ReefAPI engine.
Do I need a setlist.fm login or account?▾
No login to setlist.fm is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.
How fresh is the setlist.fm data?▾
The page example is captured from a live search call, and production requests fetch live data through ReefAPI rather than a static sample.
How many credits does the setlist.fm API use?▾
setlist.fm actions currently cost 1-3 credits per successful call. Failed or blocked calls are free. All APIs draw from one credit pool.
Can I call setlist.fm from an AI assistant or MCP client?▾
Yes. Connect ReefAPI once through MCP and your assistant can call setlistfm actions with the same key, credit pool and JSON envelope used by normal REST requests.
43 Media, Film & Knowledge APIs on the same key
One key, one credit pool, one response envelope. If you are pulling setlist.fm, you are one call away from the rest of the category — no second contract, no second integration.
Need something this API does not do?
Name the endpoint, the field, or a source we do not carry yet. We ship new APIs every week and you would be first to get the key. Real people read every message and reply the same day.
Try it on your own data before you pay anything
The call above is the real endpoint, not a recording. A free key gives you 1,000 credits, the other 693 APIs, and the same envelope everywhere.
Endpoints, parameters and credit costs on this page are read from the live catalog and cannot drift from what the API accepts. Field notes were captured on 2026-11-19.