Concerts · GET
Artist upcoming concerts
GET /partner/artist-concerts
About
Fetch every upcoming concert/tour date for a Spotify artist. Accepts artist ID, `spotify:artist:URI`, or `open.spotify.com/artist/<id>` URL. With `parsed=true` returns a flat `{ artist, concerts[], nearby }` shape; with `details=true` each concert is enriched with venue, lineup, and ticket providers.
Parameters 6
- id Required
- In
- query
- Default
- —
- Description
- Artist ID, URI, or open.spotify.com URL.
- geoHash Optional
- In
- query
- Default
- 0
- Description
- Geohash for nearby-concert prioritization. `0` = global.
- includeNearby Optional
- In
- query
- Default
- true
- details Optional
- In
- query
- Default
- false
- Description
- Enrich each concert with full concert details in parallel.
- detailsLimit Optional
- In
- query
- Default
- 20
- Description
- Max concerts to enrich per request (max 50).
- parsed Optional
- In
- query
- Default
- false
- Description
- Return a flat, normalized concert shape instead of raw GraphQL.
Request
Against https://spotify-proxy.checkleaked.cc, with the same example values the Run button sends.
| curl -X GET \ |
| "https://spotify-proxy.checkleaked.cc/partner/artist-concerts?id=4YRxDV8wJFPHPTeXepOstw&geoHash=0&includeNearby=true&details=false&detailsLimit=20&parsed=false" \ |
| -H "x-api-key: $SPOTIFY_API_KEY" |
Sample response
Live only
This endpoint has no recorded sample. Press Run to fetch a real response.
Errors
- 400
- “id” is required — a request that omits it, or sends a value of the wrong type, is rejected before it reaches Spotify.
- 404
- No Spotify item exists for the “id” that was sent. Spotify ids are 22 characters of base62, so a share link has to be reduced to the id in it first.
- 401 / 403
- The key is missing, wrong, or on a plan that does not include this endpoint. On RapidAPI the header is X-RapidAPI-Key; on the Direct Portal it is an Authorization: Bearer token; on Apify the actor supplies it.
- 429
- Rate limited. The demo on this site allows 100 requests per 15 minutes and 500 per day per visitor, inside a budget shared by every visitor. With a key it is 5 requests per second on every RapidAPI plan and 10 per second on the Direct Portal.
- 5xx
- Spotify itself failed or timed out. These are transient; retry once with a short backoff rather than immediately.
Related endpoints
The other 4 operations in the Concerts group.