Skip to content
Help Center
Log in Submit a ticket
Partner API

Partner API overview and authentication

The ANS Music Video Transfer API (v1) lets B2B partners submit music videos with metadata and assets for distribution processing. HTTPS only, authenticated with an x-api-key header.

The ANS Music Video Transfer API is a B2B interface for label and distribution partners who want to submit music videos programmatically instead of through Backstage. Each request carries the video file, a thumbnail and the release metadata; ANS Music validates it and queues it for distribution processing.

At a glance
  • Version v1
  • Transport HTTPS only
  • Auth x-api-key header
  • Audience Partner accounts

Who can use it#

The API is available to Partner accounts. If you’re on a self-serve plan and need programmatic delivery, talk to us about Partner terms — see Which plan should I choose?

Base URL#

BASE https://api.ansmusic.io [CONFIRM: production base URL and whether a sandbox exists]

All endpoints are relative to the base URL and require TLS. Plain HTTP requests are rejected.

Authentication#

Every request must include your partner API key in the x-api-key header. Keys are issued per partner account by ANS Music; request one through support or your client manager.

POST /b2b-songs/transfer HTTP/1.1
Host: api.ansmusic.io
x-api-key: YOUR_KEY
Content-Type: multipart/form-data

A missing or invalid key returns 401 Unauthorized.

Keep your key secret

Treat the API key like a password: store it in a secrets manager or environment variable, never commit it to source control, and never use it from a browser or mobile app where it can be extracted. If a key leaks, contact us to rotate it.

Endpoints#

MethodPathPurpose
POST/b2b-songs/transferSubmit a music video with its assets and metadata — reference

Postman collection#

A Postman collection with a ready-made request is available for partners. [CONFIRM: link to the Postman collection — the source page has a placeholder button]

Conventions#

  • Requests are multipart/form-data because they carry binary files; metadata fields are sent as form fields (arrays as JSON strings or repeated fields — see the endpoint reference).
  • Responses are JSON with a standard HTTP status code. Success is 201 Created.
  • Rate limits and payload limits: video up to 5 GB per request. [CONFIRM: requests-per-minute limit]

Next#

Was this article helpful?

Still stuck?

Our support team answers tickets every business day. Include your account email and the release UPC or ISRC so we can jump straight in.