FOR DEVELOPERS

Music Distribution, Built for Developers

Every part of LabelGrid is reachable over REST and documented in public. Read the docs without an account, build against the sandbox that ships with every API plan, and wire webhooks into your stack. Five ways in, from full API control to no code at all.

FIVE WAYS IN

Pick Your Integration Path

Engine

The full REST API: releases, delivery to all major DSPs, analytics and royalty data. Build your own product on the engine that runs LabelGrid.

Imprint

Imprint, the LabelGrid white-label portal: your own domain, logo, colours, fonts and outbound email, with your own subscription plans billed on your own Stripe account. Your customers never see LabelGrid. No code needed — it runs on the same engine as the REST API, so you can add Engine integrations later. Early resellers are onboarded from the waiting list.

WordPress Plugin

Sync releases to your site with LabelGrid Gate: players, smart links, pre-saves and gated downloads in WordPress.

White-Label Stack

How the API, the portal and the addons fit together for distributors running a service under their own brand.

MCP Server

Drive the whole API from your AI assistant. Connect Claude, Cursor, or any MCP client and manage releases, analytics and royalties in natural language.

DEVELOPER EXPERIENCE

Public docs, sandbox, no demo wall

You can evaluate the whole API before you talk to anyone. No login, no sales call, no demo gate. When you do want a human, every API plan carries a support SLA — a first response within two business days, and a dedicated technical account manager on Scale and Custom.

Public documentation

The complete reference is open at api.labelgrid.com/docs/api. Read every endpoint, request, and response before you commit to a plan.

Sandbox environment

Every API plan includes a sandbox so you can build and test against real endpoints without touching live deliveries or real money. Sandbox access ships with every API tier and switches on with your plan — it is not a separate request or a time-limited trial.

Help-center guides

Practical walkthroughs sit alongside the reference: the API overview and DDEX import guide.

AI-NATIVE

Drive the API from your AI assistant

Every REST endpoint has a natural-language front door. The official LabelGrid MCP server connects Claude Desktop, Claude Code, Cursor, or any Model Context Protocol client to your account, so you can draft releases, check review status, and pull analytics by asking for them.

Add one line to your client’s config and you are done — the server runs through npx and connects with your API token on first run. It is first-party and open source under the MIT license, published on npm as @labelgrid/mcp.

Make your first API call today

COMMON QUESTIONS

Frequently Asked Questions

Yes. LabelGrid offers a public REST API, documented openly at https://api.labelgrid.com/docs/api. You can read every endpoint, request, and response with no login and no sales call. Signup is self-service: the docs are open with no login and no sales call, and calling the API runs on an API plan you pick from published pricing.
Yes. A sandbox ships with every API tier and switches on with your plan, so you can build and test against real endpoints without affecting live deliveries or real money. It is part of the plan, not a time-limited trial. The documentation is public, so you can evaluate the whole API surface before you pay for anything.
LabelGrid speaks DDEX in both directions and generates compliant ERN feeds for every DSP when you submit a release for distribution. That covers the current 4.3 line (4.3.0, 4.3.1 and 4.3.2) and legacy 3.8.2, with full NewReleaseMessage and PurgeReleaseMessage support, and each DSP receives the version it requires — you never manage versions yourself. If you are migrating a catalog, DDEX import brings your existing feed in during onboarding. See the DDEX import guide in the help center for what we accept.
Register a webhook through the API and LabelGrid pushes events to you as they happen, including review-status changes and delivery updates, instead of you polling for state. You can choose which event types each endpoint receives, send test hooks, inspect delivery logs, and rotate the signing secret. Payloads are signed so you can verify they came from LabelGrid.
Everywhere LabelGrid delivers. The same network is available through the API as through the app: all major digital service providers, including Spotify, Apple Music, Amazon Music, Deezer, TIDAL and YouTube Music, plus social and UGC platforms such as TikTok and Instagram, and regional platforms on every continent. There is no reduced API delivery tier — a release submitted over REST reaches the same destinations as one submitted in the dashboard, in the DDEX ERN version each platform requires.
They are published, not negotiated. Starter API covers up to 3,000 tracks and 5 record labels with up to $35k in monthly royalty processing; Growth API up to 10,000 tracks and 25 labels with up to $115k; Scale API up to 25,000 tracks and 100 labels with up to $350k. Extra label seats are add-ons on each tier, and Custom API takes bespoke track limits with unlimited labels. API plans are billed yearly except overages. Full API access and a sandbox are on every tier — the sandbox is not metered as a trial. The complete table is on the pricing page.
A support SLA on every API plan. Starter and Growth carry a first response within two business days, and Scale and Custom add a dedicated technical account manager, with Custom SLAs available on the enterprise tier. Those are targets rather than per-ticket guarantees, and in practice the average first response is under two hours during business hours. Support is 100% human with no chatbots, and it runs on business days during working hours rather than around the clock. You reach the team that runs the platform, and the docs, sandbox and pricing are open so most of the build never needs a conversation at all.

Start Building Today

Read the docs. Build in the sandbox. See published pricing. Talking to us is optional, not a gate.