COMMON QUESTIONS
Frequently Asked Questions
Does LabelGrid have a public API?
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.
Is there a sandbox?
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.
How do I deliver via DDEX?
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.
How do I get notified when a delivery happens?
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.
Where does the API deliver to?
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.
What are the plan limits on the API?
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.
What support do API customers get?
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.