Comment by Lena Paul on "Spotify Has a Free API — Analyze Any Artist's Discography in Seconds"

Great breakdown! I've been diving into Spotify's API for my research at Soundify Premium, specifically looking at how metadata affects stream loading times. Have you noticed any significant latency differences when fetching large discographies vs. single tracks? Would love to hear your thoughts on optimizing these requests!

Thanks Lena! On the metadata side specifically, the biggest latency hits I saw were on /audio-features and /audio-analysis — those endpoints respond ~3–5× slower than /tracks for the same IDs, presumably hitting a different storage tier. For the basic metadata fields (artist, album, popularity, ISRC) caching helps a lot, but TTL has to stay short on popularity since it shifts daily. One more thing worth knowing: batching via /tracks?ids=...,... (up to 50 per call) was consistently 4–6× cheaper end-to-end vs serial single-ID calls, even with the rate-limiter applying the same token cost — so loading time benefits stack on top of API-quota savings.

For your streaming-load use case — are you measuring time-to-first-playable (TTFP) from the client side, or server-side time-to-metadata-ready? They diverged surprisingly in my runs once I started measuring both.

I'm primarily tracking client-side TTFP. The divergence is real—server-side metrics often hide the 'last mile' handshake delays, especially on mobile. Batching those track IDs really is the only way to stay under the rate-limit while keeping the UX snappy. Thanks for the heads-up on the popularity TTL; that’s a tricky one to balance! Anyways great observation on the /audio-features latency! I noticed a similar trend with different storage tiers during my performance audit for Soundify Premium.

Search Hashnode