Concerts · GET
Concert feed by location
GET /partner/concert-feed
About
List upcoming concerts in a geographic area (geoHash + geonameId, obtained from `/partner/concert-locations`). Returns paginated concert sections grouped by date. Use `details=true` to deep-search every concert in parallel and attach venue, lineup, and ticket providers.
Parameters 10
- geoHash Required
- In
- query
- Default
- —
- Description
- Spotify geohash (from `/partner/concert-locations`).
- geonameId Required
- In
- query
- Default
- —
- Description
- Geoname ID (from `/partner/concert-locations`).
- from Optional
- In
- query
- Default
- —
- Description
- Start of date range (YYYY-MM-DD).
- to Optional
- In
- query
- Default
- —
- Description
- End of date range (YYYY-MM-DD).
- radiusInKm Optional
- In
- query
- Default
- 100
- conceptUris Optional
- In
- query
- Default
- —
- Description
- Comma-separated Spotify concept URIs (e.g. `spotify:concept:rock,spotify:concept:pop`).
- paginationKey Optional
- In
- query
- Default
- —
- Description
- Pass back the `paginationKey` from a prior response.
- 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. No verified example value exists for geoHash, geonameId, so the example leaves them out and the Run dialog asks for them first.
| curl -X GET \ |
| "https://spotify-proxy.checkleaked.cc/partner/concert-feed?from=2026-09-03&to=2026-12-02&radiusInKm=100&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
- “geoHash” and “geonameId” are required — a request that omits one of them, or sends a value of the wrong type, is rejected before it reaches Spotify.
- 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.