API archive entry · source-reported
setlist.fm API
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 ... ... understand how setlist.fm works (the FAQ and the Guidelines are a good starting point), ... read this documentation carefully and ... apply for an API key (link for logged in users only) - if you're no registered user yet, then register first (it's free). If this documentation isn't enough or if you've got other things you'd like to tell us about the API, visit the API Forum . Note that the setlist.fm API is, according to the API terms of service , only free for non-commercial projects. If you're interested in using the API for commercial purposes, contact us . About this Service This service provides methods to get both setlists and components of setlists such as artists, cities, countries or venues. Supported Content Types The REST service currently supports XML (default) and JSON content. To receive a JSON response, set the Accept header to application/json . Internationalization (Please note that this is an experimental feature and does not work for all cities!) Most of the featured methods honor
Plan the first integration safely
The access fields below come from the connected directory. Their likely implementation impact is explained without assuming provider-specific behavior.
Authentication
OAuth is reported. Confirm flows, scopes, consent, token lifetime, and refresh rules.
Transport
HTTPS is not confirmed. Do not send credentials or production data until secure transport is verified.
Browser access
CORS is unknown. Treat direct browser access as unconfirmed and test before choosing a client-only architecture.
First-request sequence
- Identify the current base URL, version, and endpoint for the use case.
- Confirm how credentials are issued and where they may be stored.
- Test success, invalid input, throttling, unavailable data, and timeouts.
- Record response fields, pagination, caching, and error shapes.
- Add monitoring, retries with backoff, and an appropriate fallback.
Questions to resolve before production
Pricing and quotas
Confirm current plans, free-tier limits, overages, and request ceilings.
Endpoint coverage
Check that the operations and response fields match the intended workload.
Reliability
Look for uptime history, a status page, support routes, and service commitments.
Data and privacy
Review retention, licensing, regional processing, and compliance requirements.
Versioning
Confirm the active version, change policy, deprecation window, and migration guidance.
Developer experience
Validate SDKs, examples, error formats, pagination, and test environments.
Source reference
This page separates source-reported facts from questions that need live provider verification.