API v5 Documentation

Table of Contents

APIs powered by the data of The current API version is v5.

All valid requests to the API will begin with


[1]: See special methods

API Request Structure

You can effectively "query" for a field using the above. To find a given setlist, you can use /v5/shows/showdate/YYYY-mm-dd.json. To get all setlists containing a specific song, /v5/setlists/song/songname.json or better yet /v5/setlists/slug/url-friendly-song-name.json.

Be sure to see our example calls for more.


With each request, your API key must be included via either a POST or GET parameter. Data can be passed by URI. Your requests may be rate-limited.

You can request API keys here.

Additional Parameters

Additional parameters may be passed via query string:

e.g., /[version]/[method]/[column]/[value].[format]?order_by=[column]&direction=[direction]&apikey=[apikey]&callback=my_function


Available formats are JSON (.json) and HTML (.html). Some methods may support XML (.xml).

Data Storage

Unlike previous versions of our API, local storage is permitted, however, we request that you periodically refresh your data so that you are not presenting users outdated data.

We highly encourage you to cache frequently accessed data locally. API usage is tracked and apps that demand too much data, or data too frequently, will be disabled.

Note that API response data itself is cached for a short period. If you are looking to embed data from an in-progress show, you will need to use a special method that are forthcoming.

Attribution and Usage

Use of the API is governed by our terms of use.


Some parts of the API code use parts of a project called DB-to-API.