STOCKHOLM, March 10, 2026, 20:58 CET
Spotify is pushing back a chunk of its proposed API overhaul after facing pushback from developers of third-party music tools. While the company is giving more time before changing which API functions are available to existing Development Mode integrations, it’s not budging on new limits: a Premium account will still be required, plus a five-user maximum and one client ID allowed per developer.
That’s suddenly an issue, since Development Mode is Spotify’s test environment—and with the March 9 cutoff, smaller apps already operating faced a wall. Earlier this week, a developer pointed out that an app serving hundreds still couldn’t move up; the requirements? A registered business, plus at least 250,000 monthly active users.
Spotify described its February move as a security upgrade, arguing that new automation and AI tools had shifted the risks around developer access. The company wants Development Mode to stick to its original purpose: a space for experimentation and personal projects, not a launchpad for commercial apps or larger-scale operations.
Plenty of limits stick around. Spotify’s migration guide notes that Development Mode is now locked to Premium users, and developers only get a single client ID. Each app is capped at five authorized users. Supported endpoints are trimmed, and some legacy playlist features are now marked deprecated.
Spotify’s stance has softened, if only slightly. On its developer forum, a moderator posted that changes to endpoints are on hold following user feedback. Previously, another moderator noted that the company is revamping its one-app-per-user setup, promising to clarify how developers can upgrade from Development Mode to more advanced access.
But for certain indie builders, the harm has already landed. The solo developer behind the release-tracking bot DropTrackr said two days ago he pulled public access altogether—Spotify had yanked the new-releases endpoint, and polling at the artist level started to trigger 24-hour rate-limit bans. The higher quota threshold? Still out of reach.
The dispute couldn’t come at a trickier moment for Spotify. Back in February, Reuters noted that the company—now steered daily by co-CEOs Gustav Söderström and Alex Norström—projected first-quarter earnings ahead of Wall Street’s expectations, crediting stronger user numbers and higher prices for the boost.
Spotify pulled in roughly $17.2 billion in revenue for 2025 and netted $2.2 billion, according to Reuters company data. With that kind of muscle, executives can afford to clamp down on the platform, though the risk is higher now if they push away the smaller developers responsible for expanding Spotify’s footprint.
The overall playbook hasn’t changed: Spotify keeps pulling users deeper into its own ecosystem. Reuters noted back in January that Spotify rolled out new monetization options for video podcasters, aiming to challenge YouTube and Netflix more directly. Then in December, the company bumped up music-video access for Premium subscribers in the U.S. and Canada—another jab at YouTube.
Still, pulling back only partway might not resolve the standoff. A post from the developer community last month labeled Spotify’s fresh extended-quota rules a “full on lockout” for 99% of developers—highlighting the chance that even as Spotify guards its own turf, it risks shrinking the broader ecosystem that’s grown up around it. Spotify Community
