Beatport integration · live

Beatport API access, without the Beatport integration

A single REST interface for Beatport auth, catalogue search, listener libraries and playlist writes — sharing the exact request and response shape as 11 other music services. No Beatport developer account, no OAuth client, no token storage on your side: we hold the Beatport credentials and use them only to move a listener's own library on their behalf, the way FreeYourMusic has for ten years.

Get a sandbox key See beatport endpoints

redirect to authenticate a listener

services on the same schema

Beatport dev accounts you manage

auth · beatport

# 1 — send the listener to the hosted Beatport authorisation page.
#     Your account slug: you · returnUrl whitelisted in the dashboard.
 
https://app.musicapi.com/you/beatport/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": "beatport" }
}
 
# 3 — that UUID unlocks every Beatport user endpoint:
 
GET https://api.musicapi.com/api/6a002d4b-f95b-471f-a27d-609a42e10cdb/playlists
Authorization: Basic <clientId:clientSecret>

What you can do

Everything the Beatport API exposes, on one schema.

01AVAILABLE

Read the library

Full paged access to liked tracks and followed artists in Beatport.

02AVAILABLE

Read playlists

Owned and followed playlists with track order, artwork and descriptions intact.

03AVAILABLE

Write playlists

Create, append and reorder playlists in a listener's Beatport account, idempotently.

04AVAILABLE

Search & match

Resolve any track, album or artist to its Beatport ID, by ISRC or by text, with a confidence score.

05AVAILABLE

Catalogue metadata

Tracks, albums, artists and artwork from the public Beatport catalogue, no listener auth needed.

06AVAILABLE

Cross-service IDs

Resolve one recording to its ID on Beatport and the other 11 services at once.

07AVAILABLE

Listener profile

Display name, avatar, country and account tier, in one normalised shape.

08AVAILABLE

Raw passthrough

Need a Beatport field we don't normalise in your transfer flow? Request the underlying token for that listener.

page size: 100search by ISRC: yesreturns ISRC: yesedit playlist details: yesreturns listener country: no

Endpoints

Same routes for beatport as for the other 11.

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.

Beatport specifics

Track names carry the mix version, so an extended mix never matches the radio edit; ISRC lookups come first.

AUTH/you/beatport/authStart Beatport authentication GET/api/{userUUID}/users/profileListener profile GET/api/{userUUID}/liked/tracksLiked tracks, paged GET/api/{userUUID}/playlistsPlaylists and metadata POST/api/{userUUID}/playlistsCreate a playlist POST/public/search · beatportCatalogue search, no listener auth POST/api/{userUUID}/searchResolve a recording to its Beatport ID by ISRC

Compared to the official API

What you'd otherwise build against Beatport directly.

The official Beatport API is free. The work around it — approval, quota, auth, pagination quirks, breaking changes — is what teams actually pay for, once per service.

Concern

Direct Beatport API

MusicAPI

Getting access

Developer account, app review, quota requests per service

One key, all 12 services, live in minutes

Authentication

Your own OAuth client, redirect URIs, token storage and refresh

One hosted redirect; we hold clients and refresh tokens, used only for the transfers listeners authorise

Response shapes

Every provider models tracks, albums and playlists differently

One normalised schema across all 12

Breaking changes

You track 12 changelogs and ship fixes

We absorb them behind a versioned interface

Rate limits

Per-provider ceilings, backoff and retry logic on you

Standardised 429s with Retry-After, retries and idempotency built in

Adding a service

A new integration project each time, after Beatport

Change one string in the request

FAQ

Beatport API questions we get weekly.

Do I need my own Beatport developer account?

No. Beatport has no self-serve developer programme. MusicAPI signs users in with their Beatport username and password, so you need no keys. MusicAPI holds the Beatport 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 Beatport side, including token refresh and revocation.

Is this a wrapper around the official Beatport API?

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.

Can I still get the raw Beatport response?

Yes, for the listeners who authorised a transfer. Passthrough gives you that listener's underlying Beatport token when your transfer flow needs a field we don't normalise.

What does it cost?

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.

How long does a Beatport integration take?

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.

Start with Beatport today.

Sandbox keys are free and instant. Authenticate a real Beatport account and make your first live call within the hour.