Skip to content
Updating the Criteria for Web API Extended Access

Posted April 15, 2025

Spotify

Since launching our developer platform in 2009, we’ve been inspired by the creative tools developers have built to enhance the Spotify experience. We believe audio and video should be easy to access anytime, anywhere. This is core to our ubiquity strategy–making Spotify seamlessly available across all devices and platforms, whether it’s your phone, TV, car, or smart speaker.

As our platform evolves, we’ve identified the need to better align Spotify for Developers with our growing platform needs to support listeners, creators, and artists and ensure we allocate resources effectively to enable impactful, scalable integrations. That’s why we’re making updates to the criteria for granting extended quota mode access to the Web API. While development mode will remain accessible for experimentation and personal use, extended access will now reflect a more focused approach to fostering meaningful partnerships.

Why we’re Updating the Criteria

After thoroughly reviewing extended quota mode Web API access applications, we found that some use cases no longer align with user interests or our evolving business needs. In addition, over 95% of the applications we receive for extended Web API access fall short of basic security, privacy, and licensing standards.

As a result, we’re updating how we grant extended quota mode access to ensure we continue to invest our resources effectively while supporting use cases that are impactful and aligned with our platform strategy.

What’s Changing

Starting May 15, 2025, extended Web API access will be reserved for apps with established, scalable, and impactful use cases that help drive our platform strategy forward and promote artists and creator discovery. Developers previously granted extended access and actively using the Web API in compliance with our Developer Terms will remain unaffected by this change.

Developers with new extension requests can submit their applications through the existing framework until May 15th, 2025, and we are committed to reviewing each one. After that date, new proposals will need to meet the new criteria and Developer Terms, and the application submission process will move to our Web API page. As part of this change, we are also updating our Developer Terms, effective May 15, 2025. The changes are outlined on our Spotify Developer Terms page.

While we recognize that changes like these can raise questions, only a small portion of developers (less than 1%) should be impacted. With the vast majority of use cases never having required extended Web API access, we’re confident these changes will improve the overall experience for the broader developer community.

What’s Next

These updates reflect our commitment to supporting a secure, efficient, and aligned platform that supports Spotify's long-term goals. By focusing on impactful integrations, we aim to ensure the platform continues to evolve in alignment with our platform strategy, making Spotify seamlessly available and providing further opportunities for artist and creator discovery, all while maintaining a vibrant developer community.

If you have feedback or need support, please visit our Community Forum to connect with us.