Music licensing for apps works differently once an API is involved. Your platform signs one agreement with the music provider, and your users get permission to use tracks inside their own projects under terms your app passes through to them. The API's delivery rules are part of how that permission stays valid.
That's a different model from buying a song or connecting a consumer streaming API. A purchased track or a personal subscription gives you listening rights. It doesn't give you the right to put music inside a product your users export and publish.
This guide covers what an app music license has to include, who holds the license when music runs through an API, and what your users can do with a track. It then walks through the delivery rules written into the integration, how YouTube claims get released, and where app store rules and performance licenses fit. It closes with how to test an integration before you commit.
Music your users can export
Build music into your product on an API that handles delivery, from preview streams to final export.
What music licensing for apps actually covers
Music licensing for apps is permission to reproduce and distribute music inside a product. A recorded song usually carries two copyrights: one in the musical work and one in the sound recording. As the U.S. Copyright Office explains, the two are commonly owned and licensed separately. Buying a track or paying for a streaming subscription grants neither right for use inside an app.
Consumer music APIs don't close that gap. Apple's App Review Guidelines say MusicKit isn't a replacement for the licenses a deeper integration needs, and that an app creating audio or video files users can share to social media has to get permission from rights holders directly. Spotify's Developer Policy is blunter: developers can't synchronize sound recordings with any visual media.
If your product lets users put music under video, you're in sync territory. The ownership side (masters, publishing, mechanical and performance royalties) is laid out in our guide to types of music rights and royalties, and the video side in our explainer on sync licensing. Games raise their own questions, which is why we cover how to license music for video games separately.
Who holds the license in an API integration
In an API integration, the platform is the licensee. Soundstripe's API terms make the platform responsible for every person who uses the catalog through its app. Each end user is licensed directly by the platform and must agree to Soundstripe's Terms of Use before accessing the library, and every download they make counts against the platform's own plan.
That's the core difference from a creator subscription. Your users work inside your product, but the terms still travel with the music, and your app is where they're enforced. If you're still deciding whether an API belongs in your product at all, start with the benefits of a music API.
What your users can do with a track
Soundstripe's API terms frame end-user rights around a Project: Soundstripe music combined with the user's own original work. Inside a Project, users can search, edit, sync and monetize tracks. Your platform can license them to distribute finished Projects in any medium, as long as that use follows Soundstripe's Terms of Use. What the terms don't cover is the music on its own, outside a Project.
What your platform is responsible for
The platform carries the compliance work that a creator would otherwise handle alone. Under the API terms, that means:
- Requiring end users to accept Soundstripe's Terms of Use, with credentials they aren't allowed to share
- Monitoring usage and reporting unauthorized use promptly once you become aware of it
- Keeping each end user's agreement for three years after their account closes, with an audit of your records allowed once every 12 months
- Keeping the catalog out of any dataset used to train AI or machine learning systems
Protection against outside claims is a separate conversation from these obligations. For background, here's how indemnification works in music licensing.
How the API keeps the license intact
Delivery rules in a music API are license terms written as engineering requirements. Soundstripe's API documentation requires that audio, stems and artist images be served from Soundstripe's CDN, and client-side apps can't call the API directly. Lossless WAV files should stay off the front end until export, and the API terms allow storage on your servers only temporarily, for processing.
| Integration choice | What the docs say | Why it matters for the license |
|---|---|---|
| Nightly index (recommended) | Reindex all resources and metadata every night | Keeps CDN links current and drops tracks removed from the catalog |
| Proxy through your back end | Your client calls your server, and your server calls the API | Keeps the API key off users' devices, at the cost of added latency |
| CDN URLs | Expire in 7 days or less | Files come from Soundstripe's CDN, not a permanent copy you host |
| Preview vs export | MP3 for preview, WAV stitched on the back end at export | Users edit with previews, and the full-quality file never reaches the front end |
At scale, this is what lets a platform put licensed music inside everyday workflows. Shopee's merchants across 8 markets create over a million videos each month with Soundstripe music, and the story of licensed music at scale on Shopee shows how that works inside a commerce app.
How YouTube claims get cleared inside an integration
YouTube's Content ID scans every upload against reference files submitted by copyright owners, and a match can block, monetize or track the video. For Soundstripe songs used inside an integration, the claim is released with a code generated through the API. That code goes in the video description when the video is uploaded.
How to clear YouTube claims for songs used in your app
- Request a release code for each song
Send a request to the API's digital usages endpoint with the song's ID. Each code clears one song, so a video with three songs needs three codes.
- Give each code to the user before upload
Surface the codes in your export flow, or pass them to the client who owns the channel. The person uploading the video needs them in hand before the upload starts.
- Add the codes to the video description at upload
The codes have to be in the description at the time of upload, or the claims won't be released. Codes are single use, so every new video needs new codes.
The full request format is in Soundstripe's YouTube release code guide. Subscribers working outside an integration have other options, including listing their channel, covered in how to automatically clear YouTube content claims.
Where app store rules and performance licenses fit
App stores treat music rights as the developer's responsibility. Apple's guidelines ask that an app include only content its developer created or has a license to use, and Apple can require authorization on request. Google Play's intellectual property policy says developers may be required to provide evidence of their rights to use copyrighted content. Keep your agreement where you can produce it quickly.
Performance licenses are a separate thing. BMI's website and mobile app license covers public performance of BMI musical works through apps and websites. It doesn't include reproduction, distribution or other rights in musical works or sound recordings, so it can't stand in for the license on the music itself. Whether your app also needs one depends on how it transmits music, so confirm that with your music provider before launch. Our glossary of business music licensing terms covers the vocabulary.
How to test an integration before you commit
Soundstripe's self-serve trial key lets you start building before any contract is signed. The key is valid for 30 days and returns watermarked files. High-res files need a production key, and volume or custom licensing goes through the sales team. That's enough to build and test the full preview-to-export flow, including the YouTube code handoff.
If your team needs music for its own content rather than for a product, an API is the wrong tool. Look at Soundstripe's Enterprise plan instead.
Test it before you commit
Create a 30-day trial key and test your preview-to-export flow before you sign anything.
Frequently asked questions
Not for production use. Soundstripe's trial API key is free and valid for 30 days, but it returns watermarked files, and high-res files require a production key.
It depends on the licensing model and the scale of your platform. API access to Soundstripe's catalog starts with a conversation with the partnerships team, who scope it to your platform and use case. Licensing a commercially released song directly can mean separate agreements for the musical work and the sound recording.
Not as a substitute for the catalog license. A performance license from a performing rights organization covers public performance of that organization's musical works and doesn't include reproduction or distribution rights. Whether your app needs one alongside the catalog license depends on how it transmits music, so confirm it with your music provider.
Your platform does. Under Soundstripe's API terms, the platform licenses each end user through its app, requires them to agree to Soundstripe's Terms of Use, and is responsible for their use of the music. Every download counts against the platform's own plan.
Only as part of the export. Soundstripe's API documentation recommends streaming MP3 previews to the front end and stitching the lossless WAV onto the video on the back end at export. The API terms limit end users to using music inside their own Projects.
