When an artist releases music through your platform, getting their lyrics into Musixmatch means those lyrics appear across every product and service powered by Musixmatch data — from streaming apps to AI music experiences. The Distribution API gives you a direct, automated path to make that happen at scale.Documentation Index
Fetch the complete documentation index at: https://docs.musixmatch.com/llms.txt
Use this file to discover all available pages before exploring further.
How it works
The integration is built around four resources: artist claims, subscriptions, deliveries, and lyrics. An artist claim associates a Musixmatch user with their artist identity, using identifiers from Spotify, iTunes, or your own catalog. This is what allows Musixmatch to attribute delivered content to the right artist. A subscription event notifies Musixmatch when a user subscribes to or unsubscribes from a plan on your platform. Musixmatch maps your plan identifiers to the corresponding Musixmatch plans and grants or revokes access accordingly. A delivery is a release package — a ZIP file containing the ERN metadata and audio files for one release. Submitting a delivery makes the release known to Musixmatch and gives us the audio we need to generate time-synced lyrics. A lyrics submission associates plain-text lyrics with a specific track, identified by ISRC. You can submit lyrics yourself if you have them, or leave it to Musixmatch to AI-generate them from the audio. Either way, the output is plain-text lyrics indexed in the Musixmatch catalog. The two steps are independent by design — a delivery can arrive before lyrics are ready, and lyrics can be submitted as soon as they exist, even before release date. The only requirement is that a delivery containing the audio must be processed before AI generation can run.Register as a partner
Contact apisupport@musixmatch.com to receive your
client_id, client_secret, and partner base URL. You will also provide your redirect_uri for the OAuth flow.Authenticate
Use the Authorization Code flow to authenticate an artist in your app and retrieve their Musixmatch user ID. Use the Client Credentials flow to obtain a service-level Bearer token for your backend API calls.
Claim the artist
Call
POST /distribution/artist/claim with the user’s Musixmatch user ID and at least one artist identifier (Spotify artist ID, iTunes artist ID, or your internal artist ID). Musixmatch returns a list of claim_ids confirming the association. Use GET /distribution/artist/claim/{partner_user_id} to verify the claim was processed.Manage subscriptions
Call
POST /distribution/subscriptions when a user subscribes to a plan on your platform to activate their Musixmatch plan. Call DELETE /distribution/subscriptions/{musixmatch_user_id} when they unsubscribe to revoke access.Deliver the release
Call
POST /distribution/deliveries/files to get a pre-signed upload URL and a file_id. Upload the release ZIP to that URL, then call POST /distribution/deliveries with the file_id to create the delivery and receive a delivery_id. Poll GET /distribution/deliveries/{delivery_id} until the status is completed.Submit lyrics
Call
POST /distribution/lyrics with the track ISRC and — optionally — the plain-text lyrics. If you omit the lyrics, Musixmatch AI-generates them from the audio in the delivery. Poll GET /distribution/lyrics/{lyrics_request_id} until the status is success, at which point the plain-text lyrics are indexed in the catalog.Base URL
Each distribution partner is assigned a dedicated base URL during onboarding:Authentication
All Distribution API endpoints require a Bearer token obtained via the Client Credentials flow. ThePOST endpoints additionally require the artist’s Musixmatch user ID, which you retrieve by introspecting the user’s access token from the Authorization Code flow.