Very long Retry-After values on Web API 429

digging — Mon, 11 May 2026 06:11:09 GMT

Plan
Not applicable - Spotify Web API developer app

Free/Premium
Not applicable

Country
South Korea

Device
Server-side app on Google Cloud Run

Operating System
Node.js on Google Cloud Run

My Question or Issue

Hello,

I’m developing a music web service using the Spotify Web API with the Client Credentials flow.

Recently, our app has started receiving 429 responses on catalog detail endpoints such as:

- GET /v1/artists/{id}
- GET /v1/artists/{id}/top-tracks
- GET /v1/artists/{id}/albums
- GET /v1/albums/{id}

Search requests still appear to work, but artist and album detail requests are returning 429.

The unusual part is the Retry-After value. We are seeing very long values:

- around 66,000 seconds
- around 48,000 seconds

This means a cooldown of roughly 13 to 18 hours.

Is this expected behavior for Web API apps in development mode? Are artist and album detail endpoints subject to a separate or stricter rate limit than search?

We are planning to reduce live calls by caching metadata, but I’d like to understand whether such long Retry-After values are normal.

Thank you.

topic Very long Retry-After values on Web API 429 in Spotify for Developers

Very long Retry-After values on Web API 429