📌 Important: Spotify Developer Platform Changes (Not Controlled by This Project)

Spotify has announced upcoming changes to Spotify for Developers that will affect Development Mode applications and Web API access.

This project is a community-maintained Java API wrapper, developed by voluntary contributors and not affiliated with Spotify in any way.
The rules described below are Spotify’s decisions, not policies set or endorsed by this repository or its maintainers.

🔗 Spotify announcement: Update on Developer Access and Platform Security (Posted Feb 6, 2026)

✅ Current state of this library

• The Java API wrapper has been updated to reflect Spotify’s newly announced restrictions. The version including the changes is version version 10.0.0-RC1.
• As Spotify begins enforcing these changes, issues are expected to appear (auth failures, missing endpoint access, quota errors, etc.).
• These changes are as frustrating for maintainers as they are for users — they are imposed externally and cannot be overridden here.

Please keep in mind: if something breaks due to these changes, it is not something maintainers can “fix” on Spotify’s behalf.

🔄 Summary of what Spotify is changing

Spotify is tightening access to its developer platform, particularly for Development Mode apps.

Starting February 11, 2026 (new apps)

All newly created Development Mode Client IDs will have these restrictions:

• A Spotify Premium account is required
• One Development Mode Client ID per developer
• Up to 5 authorized users per Client ID
• Access limited to a smaller subset of Web API endpoints

Starting March 9, 2026 (existing apps)

The same rules will be applied retroactively to all existing Development Mode integrations.

🧪 What this means for users of this wrapper

• Development Mode is now explicitly limited to learning, experimentation, and personal, non-commercial use by Spotify
• Projects that previously worked may:
  • Fail authorization
  • Lose access to endpoints
  • Encounter stricter quotas or unexplained API errors
• These failures may occur without any change to this library’s code

If your app stops working around these dates, the cause is almost certainly Spotify platform enforcement, not a regression in this repository.

💬 Where to discuss these changes (please read)

Questions, complaints, or feedback about Spotify’s policy changes should not be opened as issues in this repository.

The maintainers cannot resolve platform-level decisions and do not have a direct channel to Spotify.

👉 Please direct discussion to Spotify’s official community thread instead:
https://community.spotify.com/t5/Community-Prep/February-2026-Spotify-for-Developers-update-thread/m-p/7330564

Issues opened here should be limited to:

• Wrapper bugs unrelated to Spotify policy
• Concrete PRs adapting to the new constraints
• Reproducible technical issues that can be addressed within this codebase

Thank you for understanding the limits of what a community-maintained project can realistically support under externally imposed platform changes.