Why Demus Stopped Importing Spotify Playlists: Is Spotify Silently Blocking Third-Party Apps?

Here is key findings on Why Demus Stopped Importing Spotify Playlists: Is Spotify Silently Blocking Third-Party Apps.

Spotify has spent the last two years systematically fortifying its walled garden. Under the updated Spotify Developer Terms of Service, the Swedish streaming giant has placed severe restrictions on how external applications access its Web API. Spotify explicitly prohibits developers from using its metadata to recreate or mirror the Spotify listening experience inside alternative playback engines.

In mid-2024, Spotify began deprecating unauthenticated API endpoints that third-party developers relied on to fetch public playlist information. Previously, an application could send a lightweight GET request to a public playlist URL and receive structured JSON data containing every song on the list. Today, requests sent without valid, rotating OAuth user tokens are routinely throttled or blocked outright by Cloudflare bot management layers.

When thousands of Demus users attempt to fetch playlists using shared or embedded API keys, Spotify’s servers flag the traffic spike as abusive scraping. The server issues an HTTP 429 "Too Many Requests" response or a 403 Forbidden code. The app hangs, waits for a timeout, and displays a connection failure.