Overview
The Royalti.io API supports advanced metadata fields for both Products (albums/releases) and Assets (tracks) aligned with the DDEX MEAD (Music Enrichment and Description) standard. These fields enable rich metadata delivery to Digital Service Providers (DSPs), improving discoverability and providing comprehensive release information.When to Use MEAD Fields
- Reissues and Special Editions: Track original release dates, edition types, and reissue status
- Chart-Eligible Releases: Include chart history and sequence information
- Professional Productions: Document recording/mastering locations, producers, and engineers
- Multi-Disc Releases: Specify disc counts and track totals
- Catalog Variants: Link related releases via parent release IDs
- Track-Level Enrichment: Add musical attributes like tempo, key, and mood to assets
Product MEAD Fields
Release Information
Production Credits
Chart and Performance Data
Chart History Object:
Copyright Information
Asset MEAD Fields
Assets (tracks) support their own set of MEAD enhancement fields for track-level metadata.Musical Attributes
Production Information
Classification
Additional Metadata
Quick Start
Creating a Product with MEAD Fields
- cURL
- Node.js
- Python
Creating an Asset with MEAD Fields
- cURL
- Node.js
- Python
Common Use Cases
Product: Reissued Album
When re-releasing a classic album with new mastering:For reissues,
p_line_year typically reflects the original recording year, while c_line_year reflects the new release year.Product: Deluxe Edition with Bonus Tracks
When releasing an expanded version of an album:Product: Multi-Disc Box Set
For comprehensive anthology releases:Product: Chart-Eligible Release with History
Including historical chart performance:Asset: Electronic Dance Track
Rich metadata for DJ and playlist curation:Asset: Acoustic Recording
Capturing performance details:Updating Existing Products
Add MEAD fields to existing products using the PUT endpoint:- cURL
- Node.js
- Python
Updating Existing Assets
Add MEAD fields to existing assets using the PUT endpoint:- cURL
- Node.js
- Python
Bulk Operations
Update multiple products with MEAD fields efficiently:- cURL
- Node.js
- Python
DSP Delivery Integration
MEAD fields are automatically included when delivering products to DSPs that support rich metadata.Supported Providers
DSPs that accept MEAD enhancement fields:Validation Before Delivery
When delivering products, MEAD fields are validated against provider requirements:Best Practices
Copyright Year Accuracy
Use
p_line_year for original recording year and c_line_year for the current release compilation/mastering year.Link Related Releases
Use
parentReleaseId and sequenceNumber to maintain catalog relationships between standard and deluxe editions.Production Credits
Include all relevant producers and engineers for proper attribution and improved DSP discoverability.
Reissue Documentation
Always set
originalReleaseDate when reissue is true for accurate release history.Troubleshooting
MEAD fields not appearing in DSP delivery
MEAD fields not appearing in DSP delivery
Cause: The delivery provider may not support specific MEAD fields.Solution:
- Check the provider’s supported fields in the Product Delivery guide
- Verify the fields are set before delivery
- Some fields are DDEX MEAD-specific and may not transfer via CSV delivery methods
Invalid c_line_year or p_line_year
Invalid c_line_year or p_line_year
Error:
Year must be between 1900 and 2100Solution: Ensure year values are 4-digit integers within the valid range:chartHistory validation error
chartHistory validation error
Error:
Invalid chart history formatSolution: Each chart history entry must include chart, position, and date:Invalid tempo value
Invalid tempo value
Error:
Tempo must be a positive numberSolution: Tempo should be a positive integer representing BPM (beats per minute), typically between 60-200:Asset mood or genre not appearing in DSP
Asset mood or genre not appearing in DSP
Cause: Some DSPs have their own genre/mood taxonomies and may not accept custom values.Solution:
- Use standardized mood and genre terms where possible
- Check DSP-specific documentation for accepted values
- Asset classification fields like
mood,genre, andsubGenreare best-effort mappings
Related Resources
Product API Reference
Complete product endpoint documentation
Asset API Reference
Complete asset endpoint documentation
Product Delivery
Deliver products to DSPs
Asset DDEX Management
Prepare assets for DDEX delivery
DDEX Integration
DDEX message generation
FUGA Integration
CSV-based distribution via FUGA