Restore playlist write access for Development mode apps — personal/hobbyist use is completely blocked

[lucasforbes]

Problem

Spotify's API policy changes have made it completely impossible for individual developers to build personal AI-powered tools on top of Spotify. This isn't an edge case — it's a fundamental policy failure that locks out an entire class of legitimate, harmless use.

What I'm trying to do

I'm using Claude (Anthropic's AI assistant) with a local MCP server to intelligently manage my own playlists — analyzing what's in them and adding music based on vibe, genre, and listening patterns. This accesses only my own account, with no other users involved.

What's broken

In Development mode, the following endpoints return 403 Forbidden even for the authenticated app owner accessing their own data:

• GET /playlists/{id}/tracks
• POST /playlists/{id}/tracks
• DELETE /playlists/{id}/tracks
• POST /users/{id}/playlists

Read-only endpoints like GET /me, GET /me/playlists, and playback controls work fine.

The real issue: Extended Quota is now enterprise-only

I looked up the path to getting write access restored. As of May 15, 2025, Spotify's Extended Quota eligibility requirements are:

1. Legally registered business entity
2. Active, launched commercial service
3. Minimum 250,000 monthly active users
4. Availability in key Spotify markets
5. Commercial viability
6. Terms adherence

This is not a developer quota tier. This is an enterprise contract requirement. There is zero legitimate path for an individual developer to access basic playlist write endpoints on their own account.

Why this is a bad policy

• A solo developer accessing only their own Spotify account poses zero risk to Spotify's platform, user data, or business
• The old Development mode (25-user sandbox) was a reasonable boundary — blocking write access entirely for the app owner themselves is not
• AI assistants and MCP integrations are becoming a primary way people interact with services. Spotify is actively blocking this entire category of innovation with no alternative path
• Competing music platforms do not have these restrictions for personal use

What Spotify should do

1. Allow playlist read/write access in Development mode for the authenticated app owner only — i.e., one user, accessing their own data
2. Create a lightweight personal use tier that doesn't require 250k MAUs or a registered business
3. At minimum, document clearly that these endpoints are blocked in Development mode so developers aren't wasting hours debugging 403s — the current docs do not mention this at all

Spotify's API used to be one of the best in the industry for developer experience. This policy reverses that entirely.

[krets]

Switching from /playlists/{id}/tracks to /playlists/{id}/items resolved the 403 Forbidden error for me.

February 2026 Web API Migration Guide.