Bulk Lyrics Submission
Standardized formats and methods for submitting lyrics in bulk to Musixmatch
Documentation for Partners
This document outlines the standardized formats and methods for submitting lyrics in bulk to contribute lyrical content at scale.
Last updated May 7, 2025
Overview of Accepted Formats
Musixmatch accepts lyrics submissions in several standardized formats to accommodate different partner workflows:
- CSV Musixmatch Standard Format - Method for bulk lyrics delivery primarily suitable for labels
- JSONL Format - Method for bulk lyrics delivery primarily suitable for labels
- DDEX MEAD - For partners using industry standard DDEX protocols
- Lyrics-Specific API: miss.process.post - Method for bulk lyrics delivery primarily suitable for labels
- Publisher-Specific API: work.post - For publishers to submit copyright information and lyrics associated with musical works
Submission Process
- Initial Setup: Contact Musixmatch filling this form to establish credentials and delivery method
- Test Submission: Send a small (100 tracks) batch for validation
- Feedback Integration: Address any formatting issues identified
- Production Submission: Begin regular delivery of properly formatted lyrics
Best Practices
- Data Validation: Ensure all ISRCs are valid and correctly formatted
- Lyrics Transcription: Ensure that the lyrics are transcribed as sung in the recording, following Musixmatch transcription guidelines
- Lyrics Formatting: Maintain original line breaks and paragraph structure
- Character Encoding: Verify UTF-8 encoding to preserve special characters
- Regular Updates: Establish a consistent schedule for delivering new content
- Communication: Inform Musixmatch of significant changes to your delivery format
Note that internal staff may periodically review lyrics to maintain the quality standards required by DSPs, with no impact on content integrity.
1. CSV Standard Format for Lyrics Submission
File Specifications
- File naming convention:
partnername_lyrics_YYYYMMDD.csv
- Format: CSV file (not Excel)
- Encoding: UTF-8, with or without BOM
- Delimiter: Comma (,)
- Quote character: Double quote (”)
- Used to escape values containing delimiters
- Example:
"Laser , Game", nice, 829
- Escape character: Double quote (”)
- For escaping quoted values containing quotes
- Example:
"We Will Rock You (From ""We Will Rock You"")"
Headers and Fields
Headers must appear in this exact order:
Field | Required | Description |
---|---|---|
isrc | Yes | International Standard Recording Code associated with the track |
artist | Yes | Name of the artist associated with the track |
title | Yes | Title of the track |
duration | No | Integer representing track duration in milliseconds (e.g., 240000 for 4 minutes); fill in ‘0’ if not available |
language | No | The expected language (ISO 3166-1 alpha-2 code) |
partner_id | No | Partner internal identification number |
lyrics | Yes | The lyrics as sung in the recording, following Musixmatch transcription guidelines |
Example
2. JSONL Format
The JSONL format, with each JSON object on a single line, is efficient for streaming and processing large datasets. Its line-by-line structure supports independent processing, simple appending, and efficient handling of bulk lyric submissions.
Below is a JSONL model that reflects the CSV standard format for lyrics submission.
JSON Schema
JSONL Example with Single Lyrics
JSONL Example with Multiple Lyrics
3. DDEX MEAD Standard
For partners already using DDEX standards, Musixmatch accepts lyrics submissions using DDEX MEAD (Media Enrichment and Description) version 1.1.
Different DDEX formats should be agreed upon separately.
MEAD Integration
- Standard Version: MEAD 1.1
- Official Reference: DDEX MEAD Documentation
The ISRC field is mandatory.
4. Lyrics-Specific API
API Endpoint
4.1 miss.process.post
To submit data, use the following endpoint:
Payload parameters:
Example response:
4.2 miss.process.get
To find more information about the aforementioned ID:
Example response:
To retrieve the data the developer has to set a polling to the API above.
5. Publisher-Specific API: work.post
Note: The work.post API is exclusively for publishers to submit copyright information and lyrics associated with musical works. If you are a label looking to send lyrics in bulk, please use one of the other methods listed in the documentation.
API Endpoint
For detailed information on using this API refer to our official documentation. For activation, please contact your Musixmatch representative.
This documentation is subject to updates as formats evolve. Partners will be notified of any significant changes to submission requirements.