DDEX DELIVERY

DDEX Delivery and ERN Feed Generation

DDEX delivery is how a distributor sends releases to DSPs as standardized ERN (Electronic Release Notification) XML feeds, the format Spotify, Apple Music, and other platforms ingest. LabelGrid generates these feeds and delivers them to all major DSPs, supporting ERN 3.8.2, 4.3.0, 4.3.1, and 4.3.2 for both delivery and import. Validation is automated and each platform receives the version it expects. No XML expertise required.

ERN sequencer generating DDEX feeds across versions 3.8.2 to 4.3.2

DSP DELIVERY

How does LabelGrid deliver DDEX feeds to DSPs?

Every release ships as a DDEX ERN NewReleaseMessage in the version each DSP requires, from ERN 3.8.2 to 4.3.2, and takedowns are handled with PurgeReleaseMessage. Territory-specific release dates, deal terms, and rights holders are preserved exactly as submitted, so DSPs like Spotify, Apple Music, Amazon Music, and Deezer receive a clean, valid feed every time. See the full distribution feature →

Release editor module with full metadata, audio and artwork validation
LabelGrid REST API module with public docs, sandbox and token auth

DDEX IMPORT

Can I import my existing DDEX feeds?

Yes. If you already produce DDEX with another provider, connect your existing feeds to LabelGrid’s S3 endpoint and keep delivering, with no catalog re-ingestion required. Bulk XML uploads run through automated validation, and continuous sync keeps your feed current. DDEX import is available on API plans.

HOW IT WORKS

How does DDEX feed generation work?

1. Ingest

Add releases through the dashboard, the REST API, or DDEX import. Metadata, audio, and artwork land in one catalog.

2. Validate

Every release is checked before delivery. DDEX import errors come back inline with XPath references, so fixes take minutes.

3. Deliver

Validated metadata ships as DDEX-compliant feeds to all major DSPs, each in the ERN version that platform expects.

Industry-Standard Delivery, Without the Overhead

Published pricing. No per-release fees. Free 7-day trial.

METADATA QUALITY

What metadata does LabelGrid validate before delivery?

LabelGrid checks credits, copyright lines, and locked fields on every release before the feed ships, so DSPs do not reject it.

Credits & Contributors — Performer, composition, and production credits enforced per track, matching DSP requirements.

Copyright Consistency — P-Line and C-Line data validated with year consistency checks per track.

Field Locks — Once a release is distributed, critical metadata is locked to prevent accidental changes.

Validation schematic: releases checked against DSP rules before delivery
Sandbox module: test every endpoint, ship when ready

FOR DEVELOPERS

Do I have to use DDEX, or is there an API?

You do not have to touch DDEX at all. Most partners integrate through LabelGrid’s REST API, with webhooks, a sandbox, and public docs, and the platform generates DDEX feeds downstream.

REST API First — Most partners integrate via LabelGrid’s REST API and let the platform handle DDEX formatting downstream.

Webhook Events — Real-time notifications for delivery status changes, approvals, and takedown confirmations.

Sandbox & Docs — Public interactive documentation and a sandbox environment on every API plan.

White-Label Ready — Run the whole platform under your own brand.

Explore the white-label API →

MORE FEATURES

Discover All LabelGrid Services

Distribution

Distribute music to all major platforms with advanced metadata and batch operations.

Catalog Management

Manage releases, tracks, artwork, and metadata across your entire catalog from one dashboard.

Royalty Accounting

Automated royalty splits, artist statements, expense tracking, and real-time reporting per release.

White Label & API

Run your own branded distribution platform with LabelGrid’s white-label infrastructure and REST API.

COMMON QUESTIONS

Frequently Asked Questions

DDEX (Digital Data Exchange) is the music industry’s standard format for exchanging release information between distributors and DSPs. ERN (Electronic Release Notification) messages describe releases, tracks, deal terms, and rights holders in structured XML that every major platform can ingest.
LabelGrid supports DDEX ERN 3.8.2, 4.3.0, 4.3.1, and 4.3.2. Each DSP receives feeds in the version it requires, configured per platform — you never manage versions yourself.
Yes. DDEX import is available on API plans. Connect your existing feeds to LabelGrid’s S3 endpoint for bulk XML uploads with automated validation and continuous sync — no re-ingestion of your catalog required. Step-by-step setup is covered in the DDEX import guide.
No. The platform and REST API handle DDEX formatting automatically. You submit releases through the dashboard or API, and LabelGrid generates compliant feeds for every DSP.
NewReleaseMessage for release delivery and PurgeReleaseMessage for takedowns. Territory-specific release dates, deal terms, and rights holders are preserved exactly as submitted.
Validation errors are returned inline with XPath references pointing to the exact element that failed, so your team can fix issues without guessing.
DDEX import is an optional capability on API plans (Starter API and above) with its own onboarding process. Contact our team to scope the setup.
Yes. The REST/JSON API is the primary integration path — LabelGrid converts your submissions into DDEX-compliant feeds for DSP delivery. DDEX import exists for partners whose pipelines already produce DDEX.

Start Your Free Trial

DDEX delivery, validated metadata, and feed-level control — one platform, published pricing, no per-release fees.