Accessing Enhanced Metadata
This guide will walk you through the integration steps to access the enhanced metadata MassiveMusic generates. It will walk you through the typical integration, but please be aware there are other methods to obtaining the label provided metadata so the initial step may be different than as documented here.\
1. Accessing the Standard (Licensor Provided) Metadata
1.0 Catalogue Events
The first integration step is to access the standard metadata for the catalogue. You should integrate with the Catalogue Events product, which pushes real time updates to the catalogue. The catalogue can then be stored and maintained within your own infrastructure for management of discovery and curation in your service.
Catalogue events are delivered as they're ingested by MassiveMusic, and therefore each event represents a snapshot of the release details at that time. Subsequent events should 'overwrite' the original event as they represent more recent updates to that release. There is a single event type, a Release Event. Each release event will contain metadata relating to the Artist(s), Release and Track(s) contained within that release, as well as availability data about the release.
Technical details on how to integrate with the Catalogue Events product can be found here.
2. Downloading the Enhanced (MassiveMusic Provided) Metadata
2.0 Enhanced Metadata
After ingesting the standard metadata available via the Catalogue Events product, you should then ingest the enhanced metadata available for the entire catalogue. Each track contains over 40 different enhanced metadata tags, and these are accessed via one of the below endpoints. Your agreement with MassiveMusic will dictate which enhanced metadata tags are available to you. An overview of all available enhanced metadata points is available here.
2.1 Batch Downloading
On initial integration you should access the batch request endpoint to ingest the backfill of track tags available to you. You should continue to use this endpoint if download track tags on a batch basis as new music is added to the catalogue. The endpoint requires you to post a JSON formatted body, containing up to 1000 tracks.
QUERY PARAMETER
| Data | Type | Description |
|---|---|---|
| country***** | string | ISO 2-character code of the country the service operates in. |
FORM DATA
| Attribute | Type | Description |
|---|---|---|
| trackids***** | string | A comma separated list of track ID's you want to retrieve data for. |
2.2 Individual Track, On-Demand Downloading
You should use the below endpoint to request track tags for individual tracks on an on-demand basis. This endpoint allows you to request enhanced metadata by MassiveMusic track ID.
PATH PARAMETER
| Attribute | Type | Description |
|---|---|---|
| trackid***** | int | The unique identifier of the track. |
QUERY PARAMETER
| Data | Type | Description |
|---|---|---|
| country***** | string | ISO 2-character code of the country the service operates in. |
Updated 3 months ago
