Disclaimer: To help you, we’ve listed some common issues that developers have had with our terms. Please keep in mind that your use of Spotify’s tools is always subject to the Developer Terms of Service. Final approvals for commercial use will always be left up to the discretion of Spotify and its partners. We hope these tips are useful and want to encourage you to continue building innovatively with our tools while respecting the rights of others.
Your integration may run into challenges if it includes:
- Alarms / Alert Tones: Utilizing or modifying Spotify song clips for alarm and/or alert integrations.
- Business-to-Business (B2B): Business-to-business, enterprise-facing integrations or “one to many” use cases.
- Content-saving: Enabling users to save or download Spotify content (eg. ripping songs, downloads of cover art).
- DJ/Mixes: Using Spotify’s catalog to mix multiple tracks into one without prior approval.
- Games / Trivia Quizzes: Incorporating Spotify into any gaming or quiz functionality without prior approval.
- Hi-Res Audio: Converting and/or playing audio in a higher resolution than provided by Spotify.
- Integration with 3rd party services: Enabling users to access playback from competing streaming & digital services (eg. transfer metadata directly/indirectly and/or to another competing music service).
- Content Alteration: Editing Spotify’s metadata, artwork and recordings, including making them accessible as clips (eg. equalization or booster apps).
- Synchronization: Syncing sound recordings accessed via the Spotify Platform with other recordings, lyrics and/or visual media.
- Taste Profiles: Using Spotify data to create profiles of user tastes or dynamically created playlists (i.e. algorithmically-generated playlists similar to our Discover Weekly.)
- Voice-Control: Using Spotify’s tools to build voice-enabled experiences.
- White-Labeling: Offering track playback, metadata, cover art or audio previews behind a paywall or charging as a standalone product.