Skip to main content

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:

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

Creating an Asset with MEAD Fields


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:

Updating Existing Assets

Add MEAD fields to existing assets using the PUT endpoint:

Bulk Operations

Update multiple products with MEAD fields efficiently:

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:
The validation response includes warnings for MEAD fields that may not transfer to specific providers.

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

Cause: The delivery provider may not support specific MEAD fields.Solution:
  1. Check the provider’s supported fields in the Product Delivery guide
  2. Verify the fields are set before delivery
  3. Some fields are DDEX MEAD-specific and may not transfer via CSV delivery methods
Error: Year must be between 1900 and 2100Solution: Ensure year values are 4-digit integers within the valid range:
Error: Invalid chart history formatSolution: Each chart history entry must include chart, position, and date:
Error: Tempo must be a positive numberSolution: Tempo should be a positive integer representing BPM (beats per minute), typically between 60-200:
Cause: Some DSPs have their own genre/mood taxonomies and may not accept custom values.Solution:
  1. Use standardized mood and genre terms where possible
  2. Check DSP-specific documentation for accepted values
  3. Asset classification fields like mood, genre, and subGenre are best-effort mappings

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