Push releases, manage artists and labels, monitor delivery and pull royalties from a single REST API. Your users live in your database — Move only sees you as one technical partner account.
Every request is signed with a short-lived JWT and an x-api-key header. Tokens are obtained via /auth/obtain-token/ and refreshed with /auth/refresh-token/.
A few representative endpoints — full schemas, query params and examples live in the OAS 3.0 reference.
curl -X POST https://privapi.movemusic.io/auth/obtain-token/ \
-H "x-api-key: <your_api_key>" \
-H "Content-Type: application/json" \
-d '{
"username": "partner@yourbrand.com",
"password": "••••••••"
}'
# 200 OK
{
"access": "eyJ0eXAiOiJKV1QiLC...",
"refresh": "eyJ0eXAiOiJKV1QiLC..."
}POST /releases/
Authorization: Bearer <access_token>
x-api-key: <your_api_key>
{
"title": "Aurora EP",
"primary_artist": 1842,
"label": 17,
"release_date": "2026-06-01",
"upc": null, // auto-generated if omitted
"genre": 12,
"tracks": [9421, 9422, 9423],
"ddex_stores": [1, 4, 7, 9, 12] // or "all"
}GET /ddex-delivery-confirmations/?release=8821
# 200 OK
{
"count": 42,
"results": [
{ "store": "spotify", "status": "DELIVERED", "delivered_at": "2026-05-28T09:14:02Z" },
{ "store": "apple", "status": "DELIVERED", "delivered_at": "2026-05-28T09:18:55Z" },
{ "store": "beatport","status": "REJECTED", "reason": "ARTWORK_RESOLUTION" }
]
}GET /statements/?period=2026-04&format=json
# 200 OK
{
"period": "2026-04",
"currency": "EUR",
"totals": { "gross": 12840.55, "net": 10921.46 },
"by_dsp": [ /* per-store breakdown */ ],
"by_track": [ /* per-track drilldown */ ]
}Every catalog object exposed as a clean REST resource.
Create and manage artist profiles, aliases and platform IDs.
Create releases, attach tracks and trigger delivery. Update status via /releases/update-status/.
Audio assets, ISRCs, contributors, publishers and per-track metadata.
Manage your labels and validate label-name uniqueness.
Writers, producers, mixers, performers — role assignments via /contributor-roles/.
Publisher entities for accurate split sheets and mechanical reporting.
List of every connected DSP target your account can deliver to.
Per-store delivery status, errors and acknowledgements from each DSP.
Royalty statements aggregated by period, ready for accounting export.
Generate invoices to Move and inspect prior issued invoices.
Normalized chart, playlist and stream trend data across every DSP.
Live links to each release on every DSP that accepted it.
Canonical genre & subgenre IDs accepted across all delivery targets.
Request a signed S3 URL for direct audio & artwork upload.
Submit and track feature requests from your team or sub-users.
Generates ERN 4.x messages and delivers via the right delivery protocol per partner.
Customers live in your database and auth system. Move only sees you as one technical partner.
Every API customer gets an internal admin dashboard to inspect releases, statuses and DSP feedback.
Distributors, sub-distributors and SaaS platforms that want to embed music distribution into their own product. You manage users and auth in your backend; Move powers the distribution engine behind it.
Every request must include both an Authorization header (Bearer access token) and an x-api-key header issued by Move. A referer header per Move staff instructions is also required.
No. Your users live in your database and never leave your platform. Move is invisible to them — to us you are one technical partner account.
Yes. /ddex-delivery-confirmations/ returns per-store status, errors and acknowledgements. You can also subscribe to webhook callbacks on ingestion and takedown events.
Yes — every account includes a sandbox with mocked DSP responses for end-to-end testing. Sandbox traffic is unmetered.
We pay you. You pay your customers. Move splits between your master account and Move; you handle downstream payouts to your sub-users.