René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"feat(spotify)!: major changes to the api starting 2026-02-11","articleBody":"## 📌 Important: Spotify Developer Platform Changes (Not Controlled by This Project)\n\nSpotify has announced upcoming changes to **Spotify for Developers** that will affect **Development Mode applications** and Web API access.\n\nThis project is a **community-maintained Java API wrapper**, developed by **voluntary contributors** and **not affiliated with Spotify** in any way.  \nThe rules described below are **Spotify’s decisions**, not policies set or endorsed by this repository or its maintainers.\n\n🔗 **Spotify announcement:** [Update on Developer Access and Platform Security](https://developer.spotify.com/blog/2026-02-06-update-on-developer-access-and-platform-security) (Posted Feb 6, 2026)\n\n---\n\n## ✅ Current state of this library\n\n- 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](https://github.com/spotify-web-api-java/spotify-web-api-java/releases/tag/10.0.0-RC1).\n- As Spotify begins enforcing these changes, **issues are expected to appear** (auth failures, missing endpoint access, quota errors, etc.).\n- These changes are **as frustrating for maintainers as they are for users** — they are imposed externally and cannot be overridden here.\n\nPlease keep in mind: if something breaks due to these changes, it is **not something maintainers can “fix” on Spotify’s behalf**.\n\n---\n\n## 🔄 Summary of what Spotify is changing\n\nSpotify is tightening access to its developer platform, particularly for **Development Mode** apps.\n\n### Starting **February 11, 2026** (new apps)\nAll newly created **Development Mode Client IDs** will have these restrictions:\n\n- A **Spotify Premium account** is required\n- **One Development Mode Client ID per developer**\n- Up to **5 authorized users per Client ID**\n- Access limited to a **smaller subset of Web API endpoints**\n\n### Starting **March 9, 2026** (existing apps)\nThe **same rules will be applied retroactively** to *all existing* Development Mode integrations.\n\n---\n\n## 🧪 What this means for users of this wrapper\n\n- Development Mode is now explicitly limited to **learning, experimentation, and personal, non-commercial use** by Spotify\n- Projects that previously worked may:\n  - Fail authorization\n  - Lose access to endpoints\n  - Encounter stricter quotas or unexplained API errors\n- These failures may occur **without any change to this library’s code**\n\nIf your app stops working around these dates, the cause is **almost certainly Spotify platform enforcement**, not a regression in this repository.\n\n---\n\n## 💬 Where to discuss these changes (please read)\n\nQuestions, complaints, or feedback **about Spotify’s policy changes** should **not** be opened as issues in this repository.\n\nThe maintainers **cannot resolve platform-level decisions** and do not have a direct channel to Spotify.\n\n👉 **Please direct discussion to Spotify’s official community thread instead:**  \nhttps://community.spotify.com/t5/Community-Prep/February-2026-Spotify-for-Developers-update-thread/m-p/7330564\n\nIssues opened here should be limited to:\n- Wrapper bugs unrelated to Spotify policy\n- Concrete PRs adapting to the new constraints\n- Reproducible technical issues that can be addressed within this codebase\n\n---\n\nThank you for understanding the limits of what a community-maintained project can realistically support under externally imposed platform changes.\n","author":{"url":"https://github.com/dargmuesli","@type":"Person","name":"dargmuesli"},"datePublished":"2026-02-11T10:34:51.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/445/spotify-web-api-java/issues/445"}