Skip to main content

Overview

DDEX (Digital Data Exchange) is the industry-standard XML format for communicating music metadata and rights information to Digital Service Providers (DSPs). The Royalti.io API supports generating ERN, MEAD, and PIE messages.

Authentication

DDEX endpoints require authentication. Some providers also use additional DDEX-specific authentication.

Message Types

ERN (Electronic Release Notification)

Used for delivering release metadata to DSPs:
Node.js

MEAD (Music Enrichment and Description)

Rich metadata for enhanced discovery:
Node.js

PIE (Party Information Exchange)

Rights holder information:
Node.js

DDEX Workflow

1

Configure Provider

Set up delivery credentials and preferences for each DSP.
Node.js
All provider credentials (FTP passwords, API keys, SFTP credentials) are automatically encrypted at rest using PostgreSQL pgcrypto with PGP symmetric encryption. No plaintext credentials are stored in the database.
2

Generate Message

Create DDEX XML from your release data.
The system automatically validates against XSD schemas and applies business rules.
3

Validate Message

Ensure compliance with DDEX standards.
Node.js
4

Deliver to Provider

Send via SFTP, FTP, API, or HTTP depending on provider requirements.
Node.js

Provider-Specific Configuration

Different DSPs have different requirements:
Node.js

Best Practices

Territory Management

Ensure territory configurations don’t overlap and cover 100% of intended distribution.

Deal Configuration

Set up usage rights and release dates:
Node.js

Error Handling

Implement comprehensive validation:
Node.js