A single REST interface for YouTube Music auth, catalogue search, listener libraries and playlist writes — sharing the exact request and response shape as 11 other music services. No YouTube Music developer account, no OAuth client, no token storage on your side: we hold the YouTube Music credentials and use them only to move a listener's own library on their behalf, the way FreeYourMusic has for ten years.
# 1 — send the listener to the hosted YouTube Music authorisation page.# Your account slug: you · returnUrl whitelisted in the dashboard.https://app.musicapi.com/you/youtube/auth?returnUrl=https://you.example/connected# 2 — they come back to returnUrl with ?data64=<base64>:{"integrationUserUUID": "6a002d4b-f95b-471f-a27d-609a42e10cdb","authModel": { "status": "success", "error": null },"integration": { "type": "youtube" }}# 3 — that UUID unlocks every YouTube Music user endpoint:GET https://api.musicapi.com/api/6a002d4b-f95b-471f-a27d-609a42e10cdb/playlistsAuthorization: Basic <clientId:clientSecret>
Swap the musicService value and every call below behaves identically. Public catalogue routes need no listener auth; user routes are addressed by the userUUID returned from the auth callback.
The official YouTube Music API is free. The work around it — approval, quota, auth, pagination quirks, breaking changes — is what teams actually pay for, once per service.
No. There is no official YouTube Music API. YouTube Music playlists and liked songs are YouTube playlists, reachable through the YouTube Data API with a 10,000-unit daily quota. MusicAPI holds the YouTube Music credentials and uses them solely to facilitate music transfers a listener has authorised, the same model FreeYourMusic has run for ten years. You call one API with your own key; we handle the YouTube Music side, including token refresh and revocation.
It's a transfer layer, not a general-purpose proxy. Requests hit our infrastructure, which speaks each provider's API on the listener's behalf to move their library and returns one consistent schema — plus matching, pooled quota and retries you'd otherwise write yourself.
Yes, for the listeners who authorised a transfer. Passthrough gives you that listener's underlying YouTube Music token when your transfer flow needs a field we don't normalise.
Billed per request to a music service, in buckets: €0.60 per 1,000 for the first 5M, €0.45 up to 25M, €0.30 above that, with a €500 per month minimum.
A sandbox key is instant and reading a live library takes about an hour. Production integrations typically land in two to four engineering weeks — and adding the next 11 services after that is a string change.
Sandbox keys are free and instant. Authenticate a real YouTube Music account and make your first live call within the hour.