setlist.fm /1.0/search/venues API
The /1.0/search/venues API from setlist.fm — 1 operation(s) for /1.0/search/venues.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/setlist-fm-1-0-search-venues-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
description: '<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 documentation carefully and</li>
<li>... <a href="https://www.setlist.fm/settings/api">apply for an API key</a> (link for logged in users only) - if
you''re no registered user yet, then <a href="https://www.setlist.fm/signup">register first</a> (it''s free).</li>
</ol>
</p>
<p>
If this documentation isn''t enough or if you''ve got other things you''d like to tell us about the API, visit the
<a href="https://www.setlist.fm/forum/setlistfm/setlistfm-api">API Forum</a>.
</p>
<p>
Note that the setlist.fm API is, according to the <a href="https://www.setlist.fm/help/api-terms">API terms of
service</a>, only free for non-commercial projects. If you''re interested in using the API for commercial purposes,
<a href="https://www.setlist.fm/contact">contact us</a>.
</p>
<h2>About this Service</h2>
<p>
This service provides methods to get both setlists and components of setlists such as artists, cities, countries or
venues.
</p>
<h2>Supported Content Types</h2>
<p>
The REST service currently supports XML (default) and JSON content.
</p>
<p>
To receive a JSON response, set the <code>Accept</code>
<a href="https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.1">header</a> to <em>application/json</em>.
</p>
<h2>Internationalization</h2>
<p>
<small>(Please note that this is an experimental feature and does not work for all cities!)</small>
</p>
<p>
Most of the featured methods honor the <code>Accept-Language</code>
<a href="https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.4">header</a>. This header is used for
localizing cities and countries. The default language is English (en), but you can provide any of the languages
Spanish (es), French (fr), German (de), Portuguese (pt), Turkish (tr), Italian (it) or Polish (pl).
</p>
<p>
E.g. if you search a setlist for a concert that took place in Vienna and you pass "de" as header, you''ll
get <em>"Wien, Österreich"</em> instead of <em>"Vienna, Austria"</em>.<br/>
This also works if you use a different language than the country''s native language.
</p>
<p>
E.g. for a concert in New York, you''ll get <em>"Nueva York, Estados Unidos"</em> instead of <em>"New
York, United States"</em> if you pass "es" as language.
</p>
<h2>API Keys</h2>
API keys (<a href="https://www.setlist.fm/settings/api">application form</a>) must be included in the request with
the <code>x-api-key</code> header.
<h2>Version History</h2>
<table class="table table-bordered table-versions">
<thead>
<tr>
<th>Version</th>
<th>Docs</th>
<th>End of Service</th>
</tr>
</thead> <tbody>
<tr>
<td><strong>1.0</strong></td>
<td><a href="/docs/1.0">Docs</a></td>
<td>-</li>
</tr>
<tr>
<td><strong>0.1</strong></td>
<td></td>
<td>December 31, 2017</li>
</tr>
</tbody>
</table>'
version: '1.0'
title: setlist.fm /1.0/artist/{mbid} /1.0/artist/{mbid} /1.0/search/venues /1.0/search/venues API
servers:
- url: /rest
tags:
- name: /1.0/search/venues
paths:
/1.0/search/venues:
get:
tags:
- /1.0/search/venues
summary: Search for venues.
description: Search for venues.
operationId: resource__1.0_search_venues_getVenues_GET
parameters:
- name: cityId
in: query
description: the city's geoId
schema:
type: string
- name: cityName
in: query
description: name of the city where the venue is located
schema:
type: string
- name: country
in: query
description: the city's country
schema:
type: string
- name: name
in: query
description: name of the venue
schema:
type: string
- name: p
in: query
description: the number of the result page you'd like to have
schema:
type: integer
default: '1'
- name: state
in: query
description: the city's state
schema:
type: string
- name: stateCode
in: query
description: the city's state code
schema:
type: string
responses:
'200':
headers: {}
description: Success
content:
application/xml:
schema:
description: ''
$ref: '#/components/schemas/json_Venues'
application/json:
schema:
description: ''
$ref: '#/components/schemas/json_Venues'
example:
venue:
- city:
id: '5357527'
name: Hollywood
stateCode: CA
state: California
coords: {}
country: {}
url: https://www.setlist.fm/venue/compaq-center-san-jose-ca-usa-6bd6ca6e.html
id: 6bd6ca6e
name: Compaq Center
- city:
id: '...'
name: '...'
stateCode: '...'
state: '...'
coords: {}
country: {}
url: '...'
id: '...'
name: '...'
total: 42
page: 1
itemsPerPage: 20
components:
schemas:
json_Coords:
type: object
title: coords
properties:
long:
example: -118.3267434
description: The longitude part of the coordinates.
type: number
lat:
example: 34.0983425
description: The latitude part of the coordinates.
type: number
example:
long: -118.3267434
lat: 34.0983425
description: Coordinates of a point on the globe. Mostly used for Cities.
json_City:
type: object
title: city
properties:
id:
example: '5357527'
description: unique identifier
type: string
name:
example: Hollywood
description: 'the city''s name, depending on the language valid values are e.g. <em>"Müchen"</em> or
<em>Munich</em>'
type: string
stateCode:
example: CA
description: 'The code of the city''s state. For most countries this is a two-digit numeric code, with which the state can be
identified uniquely in the specific Country. The code can also be a String for other cities. Valid
examples are <em>"CA"</em> or <em>"02"</em>
which in turn get uniquely identifiable when combined with the state''s country:
<em>"US.CA"</em> for California, United States or <em>"DE.02"</em> for Bavaria, Germany
For a complete list of available states (that aren''t necessarily used in this database) is available in
<a href= "http://download.geonames.org/export/dump/admin1CodesASCII.txt">a textfile on geonames.org</a>.
Note that this code is only unique combined with the city''s Country. The code alone is
<strong>not</strong> unique.'
type: string
state:
example: California
description: The name of city's state, e.g. <em>"Bavaria"</em> or <em>"Florida"</em>
type: string
coords:
description: The city's coordinates. Usually the coordinates of the city centre are used.
$ref: '#/components/schemas/json_Coords'
country:
description: The city's country.
$ref: '#/components/schemas/json_Country'
example:
id: '5357527'
name: Hollywood
stateCode: CA
state: California
coords:
long: -118.3267434
lat: 34.0983425
country:
code: US
name: United States
description: 'This class represents a city where Venues are located. Most of the original city data was taken from
<a href="http://geonames.org/">Geonames.org</a>.'
json_Venue:
type: object
title: venue
properties:
city:
description: the city in which the venue is located
$ref: '#/components/schemas/json_City'
url:
example: https://www.setlist.fm/venue/compaq-center-san-jose-ca-usa-6bd6ca6e.html
description: the attribution url
type: string
id:
example: 6bd6ca6e
description: unique identifier
type: string
name:
example: Compaq Center
description: 'the name of the venue, usually without city and country. E.g. <em>"Madison Square Garden"</em> or
<em>"Royal Albert Hall"</em>'
type: string
example:
city:
id: '5357527'
name: Hollywood
stateCode: CA
state: California
coords:
long: -118.3267434
lat: 34.0983425
country:
code: US
name: United States
url: https://www.setlist.fm/venue/compaq-center-san-jose-ca-usa-6bd6ca6e.html
id: 6bd6ca6e
name: Compaq Center
description: 'Venues are places where concerts take place. They usually consist of a venue name and a city - but there are also
some venues that do not have a city attached yet. In such a case, the city simply isn''t set and the city and country
may (but do not have to) be in the name.'
json_Venues:
type: object
title: venues
properties:
venue:
description: result list of venues
type: array
items:
$ref: '#/components/schemas/json_Venue'
total:
example: 42
description: the total amount of items matching the query
type: number
page:
example: 1
description: the current page. starts at 1
type: number
itemsPerPage:
example: 20
description: the amount of items you get per page
type: number
example:
venue:
- city:
id: '5357527'
name: Hollywood
stateCode: CA
state: California
coords: {}
country: {}
url: https://www.setlist.fm/venue/compaq-center-san-jose-ca-usa-6bd6ca6e.html
id: 6bd6ca6e
name: Compaq Center
- city:
id: '...'
name: '...'
stateCode: '...'
state: '...'
coords: {}
country: {}
url: '...'
id: '...'
name: '...'
total: 42
page: 1
itemsPerPage: 20
description: A Result consisting of a list of venues.
json_Country:
type: object
title: country
properties:
code:
example: US
description: 'The country''s <a href= "http://www.iso.org/iso/english_country_names_and_code_elements" >ISO code</a>. E.g.
<em>"ie"</em> for Ireland'
type: string
name:
example: United States
description: 'The country''s name. Can be a localized name - e.g. <em>"Austria"</em> or
<em>"Österreich"</em> for Austria if the German name was requested.'
type: string
example:
code: US
name: United States
description: This class represents a country on earth.