Reconsider daily quota limits for playback endpoints

Inzanity — Wed, 11 Mar 2026 20:43:10 GMT

Hello Spotify Team,

I would like to raise a concern regarding the current daily API quota limits, specifically when interacting with the /me/player endpoint.

I maintain a application, a companion tool used by livestreamers to integrate Spotify playback with Twitch chat and stream overlays. The app currently has around 12,000–15,000 monthly active users.

A core part of the application depends on retrieving the current playback state via:

GET /me/player

This allows the app to synchronize Spotify playback with features such as:

song request queues
playback controls
skip voting systems
real-time stream overlays
"now playing" widgets

Even with relatively conservative polling (~30 requests per minute), it is possible to reach the daily quota limit during normal usage.

Once the quota limit is reached, the application can no longer retrieve playback information for the rest of the day, or for a long period of time (I encountered a 429 with a retry-after of 6500s (~ 1h50m). For users this results in:

playback detection no longer updating
song request queues becoming unreliable
overlays and widgets showing outdated information
core functionality effectively breaking

For heavy users (for example active streamers running the tool throughout their entire stream), this can happen during normal usage patterns.

Currently, the /me/player endpoint does not have an event-based alternative such as webhooks, push notifications, or WebSocket subscriptions. As a result, polling is the only viable mechanism to keep playback state synchronized.

Reducing polling frequency significantly impacts usability, since playback changes (new track, pause, skip, etc.) would take much longer to detect.

A few possible approaches that could help developers building applications around playback state:

Increase daily quota limits for playback-related endpoints such as /me/player.
Provide separate quota pools for state polling endpoints.
(Unlikely but the best method IMO) Introduce event-driven playback updates (webhooks or subscriptions).
Provide official polling recommendations that allow near real-time synchronization while remaining within quota limits.

Spotify's API enables a lot of creative integrations in the streaming ecosystem, and tools like mine depend heavily on reliable access to playback state.

Any reconsideration of the current quota limits or introduction of event-driven updates would significantly improve reliability for applications built on top of the Spotify platform.

topic Reconsider daily quota limits for playback endpoints in Spotify for Developers

Reconsider daily quota limits for playback endpoints