https://community.spotify.com/t5/Spotify-for-Developers/Spotify-API-returning-extremely-high-Retry-After-value-68167/m-p/7502369#M21692 <P>Hello Team, I am building a personal Spotify analytics project using the Spotify Web API and Snowflake. I am currently in Development Mode and I am trying to enrich my listening history data with additional metadata. Use case I have around 40,000 unique tracks extracted from my Spotify Extended Streaming History.</P><P>My pipeline is:</P><P>Extract unique track_id values from my listening history.</P><P>Call the Track API endpoint to retrieve metadata and get the associated artist_id. Deduplicate artists.</P><P>Call the Artist API endpoint to retrieve additional information, mainly: artist genres, popularity</P><P>I am running this extraction through a Snowflake stored procedure using Python/Snowpark.</P><P>Problem During the extraction, my API calls started returning: HTTP 429 Too Many Requests Retry-After: 68167, this means Spotify is asking me to wait approximately 19 hours before retrying.</P><P>What is surprising is that: The extraction was running successfully before this happened. I am not running multiple applications using the same Spotify account. I am respecting batching where possible.</P><P>The procedure has checkpointing, so it does not restart from zero. Questions Is a Retry-After value of ~68,000 seconds expected behavior for the Spotify Web API? Does Spotify progressively increase the cooldown period if an application keeps hitting rate limits?</P><P>Is there a recommended request rate limit for Development Mode applications?</P><P>Is there a recommended architecture for this type of use case (tens of thousands of tracks → artists → genres)?</P><P>My current approach is to: cache already processed track IDs and artist IDs, batch requests, wait according to the Retry-After header, avoid unnecessary duplicate API calls.</P><P>Any advice would be appreciated. Thanks!</P> Thu, 16 Jul 2026 16:46:59 GMT pizzapete7 2026-07-16T16:46:59Z https://community.spotify.com/t5/Spotify-for-Developers/Spotify-API-returning-extremely-high-Retry-After-value-68167/m-p/7502369#M21692 <P>Hello Team, I am building a personal Spotify analytics project using the Spotify Web API and Snowflake. I am currently in Development Mode and I am trying to enrich my listening history data with additional metadata. Use case I have around 40,000 unique tracks extracted from my Spotify Extended Streaming History.</P><P>My pipeline is:</P><P>Extract unique track_id values from my listening history.</P><P>Call the Track API endpoint to retrieve metadata and get the associated artist_id. Deduplicate artists.</P><P>Call the Artist API endpoint to retrieve additional information, mainly: artist genres, popularity</P><P>I am running this extraction through a Snowflake stored procedure using Python/Snowpark.</P><P>Problem During the extraction, my API calls started returning: HTTP 429 Too Many Requests Retry-After: 68167, this means Spotify is asking me to wait approximately 19 hours before retrying.</P><P>What is surprising is that: The extraction was running successfully before this happened. I am not running multiple applications using the same Spotify account. I am respecting batching where possible.</P><P>The procedure has checkpointing, so it does not restart from zero. Questions Is a Retry-After value of ~68,000 seconds expected behavior for the Spotify Web API? Does Spotify progressively increase the cooldown period if an application keeps hitting rate limits?</P><P>Is there a recommended request rate limit for Development Mode applications?</P><P>Is there a recommended architecture for this type of use case (tens of thousands of tracks → artists → genres)?</P><P>My current approach is to: cache already processed track IDs and artist IDs, batch requests, wait according to the Retry-After header, avoid unnecessary duplicate API calls.</P><P>Any advice would be appreciated. Thanks!</P> Thu, 16 Jul 2026 16:46:59 GMT https://community.spotify.com/t5/Spotify-for-Developers/Spotify-API-returning-extremely-high-Retry-After-value-68167/m-p/7502369#M21692 pizzapete7 2026-07-16T16:46:59Z