Skip to the content
Get an API key
  1. Docs
  2. Get started

Overview

Core + Managed TransfersGuide · 2 min
What MusicAPI is, how MusicAPI Core and MusicAPI Managed Transfers differ, and which one you need.

MusicAPI connects your users to their music services. One API reads and writes playlists, liked tracks, albums and artists on Spotify, Apple Music, YouTube, Tidal, Amazon Music, Deezer and the other supported services. It also searches and matches the catalogs of those services, with no connected user.

You use MusicAPI in one of two ways.

Two products

MusicAPI CoreMusicAPI Managed Transfers
What you getA REST API. You build the screens and the transfer logic.A hosted, white-label transfer flow. You send users to a link.
Who signs users inThe hosted sign-in, or your own UI that links to itThe hosted wizard, both sides
Who matches tracksYou, with the catalog search and match endpointsMusicAPI
What your backend doesCalls /api/{integrationUserUUID}/… for each read and writeListens to webhooks, reads the Match Results API
BrandingYour appYour logo, colours, fonts and custom domain on our pages
Start hereQuickstart: CoreQuickstart: Managed Transfers

Both products share one account, one pair of API keys and one hosted sign-in.

Which one do I need

  • You want users to move their library into your service, and you do not want to build a wizard. Use Managed Transfers. The flow reads the source library, matches every item, writes it to your service and reports what it could not match.
  • You want library data inside your own product: show a user's playlists, save tracks to their account, build your own transfer or sync feature. Use Core.
  • You only need catalog data: search a track on several services, resolve a shared link, read a public playlist. Use the catalog endpoints of Core. They need no connected user.

You can start with one and add the other later.

How a Core integration works

  1. 01
    Sign in
    Your user connects a music service on the hosted sign-in.
  2. 02
    Callback
    You get the integrationUserUUID on your return URL.
  3. 03
    API calls
    Your backend calls /api/{integrationUserUUID}/playlists and the other library routes.

How Managed Transfers works

  1. 01
    Link
    You send the user to your transfer URL.
  2. 02
    Wizard
    The user connects both services and picks the content.
  3. 03
    Transfer
    MusicAPI matches and writes every item.
  4. 04
    Webhooks
    Your backend gets the result and the unmatched items.

The base URLs

HostWhat it serves
https://api.musicapi.comThe API. Every endpoint in the API reference.
https://app.musicapi.comThe dashboard (/admin), the hosted sign-in (/{slug}) and the transfer wizard (/{slug}/transfer).

Next steps