The music recommendation API that starts from an ISRC.
Send a track, an artist or a genre. Get back similar tracks, similar artists or a full playlist as ISRCs, ranked by score. Limit every answer to your own catalogue, and make it personal with your listeners' plays and skips.
curl 'https://api.musicapi.com/public/recommendations/similar-tracks?isrc=USUM71900764&limit=10' \-u '<Client ID>:<Client Secret>'# 200 OK · example values{"modelVersion": "20261114T020000Z","basis": "track","tracks": [{"isrc": "XXMAP2600001","title": "Example title","artist": { "id": "<artist id>", "name": "Example artist" },"score": 0.9412},{"isrc": "XXMAP2600002","title": "Another title","artist": { "id": "<artist id>", "name": "Another artist" },"score": 0.9187}# … 8 more tracks]}
Seed in, ranked ISRCs out.
We analyse no audio. The model learns which tracks listeners put on the same playlists, across music services, and we train it again every week.
Send what you know
One ISRC, an artist id or a genre. A playlist takes up to 50 ISRCs, 50 artists and 20 genres. A negative weight steers away from a seed.
A vector for each track
An item2vec model, trained on 15.8 million playlists, places tracks that listeners put together near each other. We train it again every week.
Ranked ISRCs
Tracks ranked by score, up to 1. By default at most 2 tracks of one artist. Each answer names the model version that made it.
Six jobs, one prefix.
Every route starts with /public/recommendations. Use your Client ID and Client Secret, as for every MusicAPI call. The routes that write or read listener data need the Client Secret.
Recommend only what you can play.
Upload the ISRCs you hold the rights to. Add catalogue=<id> to a call and every answer comes from that list, with your own ISRC of each track.
Built on what listeners put together, not on audio.
Three meters. One invoice.
You pay for the calls you make, the listeners you personalise for and the ISRCs you host. Rates go down as volume goes up, within each calendar month.
Recommendations have no minimum spend. The €500 minimum monthly spend applies only to standard requests with MusicAPI's managed credentials. Docs sandbox calls are free.
See full pricing →Questions before your first call.
Do I need to upload a catalogue?
No. Without catalogue, answers come from the whole MusicAPI catalogue: about 14 million tracks with a vector. Upload a catalogue when you can play only your own licensed tracks. Then every answer comes from your ISRCs.
Which ISRCs work as a seed?
Any ISRC of the track. We accept dashes, spaces and lower case. When a track has no vector yet, the answer uses its artist's vector and says basis: "artist". /playlist returns the seeds that match nothing in unresolved.
How fresh are the recommendations?
We train the model again every week on new playlist data. Every answer carries modelVersion. We cache answers for one model version, so a new model gives new answers.
What personal data do you keep, and how do I delete it?
An event holds your own listener id, an ISRC, the event type and the time. We need no names and no email addresses. DELETE /public/recommendations/users/{userId} deletes every event of one listener, for example when they delete their account.
How do you meter it?
With three meters: recommendation requests per 1,000 calls, personalised users per listener a month, and catalogue hosting per million ISRCs. They go on the same monthly invoice as your transfer requests. Recommendations have no minimum spend. The €500 minimum monthly spend applies only to standard requests with MusicAPI's managed credentials.
Can I try it before I pay?
Yes. Sign in to the docs and call every read route from its docs page. Docs sandbox calls are free and do not count on your usage.
Get your first recommendations today.
Sign up, copy your Client ID and Client Secret, and call /similar-tracks. Or try every read route in the docs sandbox first.