Licensing
Overview

Licensing

The Licensing API issues a license that clears a Slipstream track for use in one of your end users' videos on YouTube and other video platforms. When a platform's automated copyright system flags the track (Content ID or its equivalent), the license code is the proof you submit to resolve the claim.

You call one endpoint with a track and a user. You get back a license identifier, which you turn into a public URL. Attach that URL to the user's upload, or keep it on hand to settle any claim that comes in.

How it works

  1. Your end user picks a Slipstream track in your product.
  2. Your backend calls the Licensing API with the track ID and your user's ID.
  3. Slipstream returns a license identifier (license_id).
  4. You build the public license URL by prefixing the identifier with https://license.slipstreammusic.com/v/.
  5. You attach that URL to the user's project, embed it in the export, store it in your database, or all three.
  6. The user (or anyone they share the work with) can open the URL to see the license details.

The page at that URL is human-readable proof that the track is licensed for that specific user and project.

Who is it for?

Products where end users will publish videos containing Slipstream music on YouTube or another video platform. Common cases:

  • Video editing tools that obtain a license when the user exports a video for upload.
  • Content creation platforms that fetch a license alongside every video upload.
  • AI agents that generate videos with a Slipstream score and ship the license with the output.

If your end users will publish on a video platform that runs automated content recognition, this is the endpoint you need.

Authentication

The Licensing API uses a partner API key, not a regular user token. You receive the key when your partnership is set up. Send it on every call:

Authorization: Bearer <PARTNER_API_KEY>

Every call also requires X-User-ID, identifying the end user inside your product. This is your identifier, not a Slipstream user ID.

X-User-ID: <your_users_id>

The license is bound to that user. If the same user licenses the same track twice with the same project_name, you get back the same license.

Quotas

Each partner has a daily and a monthly quota. Every successful response includes a usage block so you can track how close you are to the limit.

"usage": {
  "daily_used": 12,
  "monthly_used": 305,
  "daily_limit": 1000,
  "monthly_limit": 30000
}

If you hit the limit, you'll get a throttled error. Quotas reset at midnight UTC for daily, and on the 1st of the month for monthly.

Endpoint reference

For request and response details, errors, and code examples, see the Generate a license endpoint reference.