Cache · POST
Invalidate cache
POST /cache/invalidate
About
Invalidate cache is a POST endpoint in the Cache group of the Spotify Data API. The spec declares no query or path parameters for it. It takes an optional JSON request body with 2 fields: key (string) and pattern (string). No recorded sample exists for it; press Run to fetch a live response.
Parameters
No parameters
The spec declares no query or path parameters for this endpoint; it takes a JSON request body instead.
Request body application/json
- key Optional
- Type
- string
- pattern Optional
- Type
- string
Request
Against https://spotify-proxy.checkleaked.cc, with the same example values the Run button sends.
| curl -X POST \ |
| "https://spotify-proxy.checkleaked.cc/cache/invalidate" \ |
| -H "x-api-key: $SPOTIFY_API_KEY" \ |
| -H "Content-Type: application/json" \ |
| -d '{}' |
Sample response
Live only
This endpoint has no recorded sample. Press Run to fetch a real response.
Errors
- 400
- This endpoint takes no query or path parameters and its JSON body is optional, so a 400 means a field in the body carries a value of the wrong type — “key” and “pattern”.
- 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 operation in the Cache group.