Both get releases into stores. Here is how each works, where each is used, and why the best delivery systems use both behind one simple interface.
DDEX delivery sends each release as an ERN XML message — tracks, artwork, metadata, territories and deals — together with audio and artwork files, usually in SFTP, S3 or Aspera batches. The store processes the batch and returns an acknowledgement. It is the industry standard for the largest stores.
API delivery sends release data through a web API, normally as JSON, and gets an immediate response. Some platforms and partners accept content this way, and modern distribution systems expose APIs so their own clients can submit releases from their apps.
Use DDEX for stores that require it and for large catalogue deliveries. Use APIs where a platform offers one, and to let your own clients' software integrate with you. Almost every serious distributor needs both.
The Plans Global approach is API in, DDEX or store API out: clients send simple JSON to one API; the system builds the right ERN version for DDEX stores, calls store APIs where available, and reports every status through webhooks.
| Aspect | DDEX ERN delivery | API delivery |
|---|---|---|
| Format | XML (ERN 3.8.2 / 4.x) | Usually JSON |
| Transport | SFTP · S3 · Aspera batches | HTTPS requests |
| Feedback | Acknowledgement messages | Immediate responses + webhooks |
| Best for | Major stores, bulk catalogues | App integrations, partner platforms |
| Effort to build | High — schemas and store profiles | Medium — per-API integration |
| Plans Global | Global Distribution Hub | API music delivery system |
A product demo, a DDEX integration, a white-label platform, a CRM, a website, an app or an automation — share a few lines and we reply within one business day, in English or Hindi.