concertarchives.org APIconcertarchives.org ↗
Access concert history, performer profiles, setlists, and venue data from Concert Archives via 4 REST endpoints. Search performers, concerts, and repertoire.
curl -X GET 'https://api.parse.bot/scraper/1c8b7b2a-4685-482e-802b-ebf2c3d135db/search_performers?page=1&query=Beatles' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for performers (bands, orchestras, etc.) by name. Returns paginated results with performer name, slug, and concert count.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination. |
| queryrequired | string | Search query for the performer name. |
{
"type": "object",
"fields": {
"page": "integer, current page number",
"results": "array of objects with keys: name (string), slug (string), concert_count (integer)",
"has_next": "boolean, whether more pages are available"
},
"sample": {
"data": {
"page": 1,
"results": [
{
"name": "The Bootleg Beatles",
"slug": "the-bootleg-beatles",
"concert_count": 1488
},
{
"name": "The Beatles",
"slug": "the-beatles",
"concert_count": 1335
}
],
"has_next": true
},
"status": "success"
}
}About the concertarchives.org API
The Concert Archives API exposes 4 endpoints covering performer search, concert history, setlists, and event details from concertarchives.org. Use search_performers to find bands or orchestras by name and retrieve their slugs, then feed those into get_performer_concerts to pull a paginated timeline of dated shows with venues. get_concert_details returns the full picture: performers, setlists broken down by artist, and location data for any individual concert.
Performer Search and Concert History
search_performers accepts a query string and returns paginated results — each with a name, slug, and concert_count. The slug field is the key input for get_performer_concerts, which returns a chronological list of concerts for that performer. Each concert record includes date, title, venue, and a slug you can pass downstream to retrieve full details. Both endpoints support a page integer parameter and return a has_next boolean for cursor-style pagination.
Concert Detail and Setlists
get_concert_details is the richest endpoint. Given a concert slug (sourced from either get_performer_concerts or search_concerts), it returns the canonical url, date, title, venue, location (city/region/country), a performers array with names and slugs, and a setlists array. Each setlist object contains the performer name and a songs array of strings — making it possible to reconstruct what was played and by whom at a specific event.
Concert Keyword Search
search_concerts lets you query concerts directly by keyword rather than going through a performer first. Results include date, title, slug, and venue_location as a combined string. This is useful when you know an event name or venue but not the performing artist. Like the other endpoints, it paginates via page and has_next.
Data Shape Notes
All date fields are returned as strings; format consistency depends on how the source records each entry. The setlists array in get_concert_details may be empty for concerts where repertoire was not logged. The performers array on a concert detail can include multiple acts, each with their own slug usable in subsequent performer lookups.
- Build a setlist tracker that maps a band's song history across concerts using
setlists[*].songsfromget_concert_details. - Generate a venue-performance timeline for a classical orchestra by chaining
search_performersandget_performer_concerts. - Identify which artists co-performed at specific events using the
performersarray in concert detail responses. - Create an artist discography companion that links studio recordings to confirmed live performances by date.
- Research how often a specific piece of music has been performed by querying setlists across multiple performer histories.
- Aggregate concert counts per performer from
search_performersresults to rank touring activity. - Cross-reference venue strings from
get_performer_concertsto map historical performance locations geographically.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Concert Archives have an official developer API?+
What does `get_concert_details` return beyond basic event info?+
setlists — an array where each object has a performer name and a songs array of strings listing what was played — plus a performers array with slugs, venue, location (city/region/country), and the canonical url for the concert page. It is the only endpoint that exposes repertoire data.Can I filter performer concerts by date range or venue?+
get_performer_concerts returns the full paginated concert history for a performer without date-range or venue filters. You can fork this API on Parse and revise it to add filtering parameters to the endpoint.Are ticket purchase links or event attendance figures included?+
How should I handle concerts where the setlist is empty?+
setlists array in get_concert_details may return as an empty array when repertoire was not recorded for that event on Concert Archives. This is a data-availability limitation of the source, not an API error. Check setlists.length before processing song data.