# Massive Music API Documentation
> Documentation for Massive Music API
## Guides
- [Introduction](https://docs.massivemusic.com/docs/guides-introduction.md)
- [Building a Subscription Streaming Service](https://docs.massivemusic.com/docs/building-a-streaming-service.md): Build a subscription streaming service using Catalogue Events, user provisioning, subscription management, streaming, optional offline playback, playlists, and reporting.
- [Building a Fitness Service](https://docs.massivemusic.com/docs/building-a-fitness-service.md)
- [Building a Download Service](https://docs.massivemusic.com/docs/building-a-download-service.md)
- [Building a Background Music Service](https://docs.massivemusic.com/docs/building-a-background-music-service.md)
- [Building a Interactive Radio Streaming Service](https://docs.massivemusic.com/docs/building-a-interactive-radio-streaming-service.md)
- [Building a Social Media Service (MassiveMusic managed content delivery)](https://docs.massivemusic.com/docs/building-a-social-media-service-direct-streaming.md)
- [Building a Social Media Service (Self managed content delivery)](https://docs.massivemusic.com/docs/building-a-social-media-service-self-managed-content-delivery.md)
- [Building a Streaming Service](https://docs.massivemusic.com/docs/building-a-streaming-service-1.md)
- [Building a Content Delivery Service](https://docs.massivemusic.com/docs/building-a-content-delivery-service.md)
- [Accessing the Songtradr Pre-Cleared Catalogue](https://docs.massivemusic.com/docs/accessing-the-represented-catalogue.md)
- [Accessing Enhanced Metadata](https://docs.massivemusic.com/docs/accessing-enhanced-metadata.md)
- [Catalogue Events Overview](https://docs.massivemusic.com/docs/catalogue-events.md)
- [Technical Specification](https://docs.massivemusic.com/docs/technical-specification-1.md)
- [Standard Metadata](https://docs.massivemusic.com/docs/available-metadata.md)
- [Standard Metadata Event Schema](https://docs.massivemusic.com/docs/standard-metadata-event-schema.md)
- [Enhanced Metadata](https://docs.massivemusic.com/docs/enhanced-metadata-tags.md)
- [Enhanced Metadata Event Schema](https://docs.massivemusic.com/docs/enhanced-metadata-event-schema.md)
- [Classes Overview](https://docs.massivemusic.com/docs/classes-overview.md)
- [Understanding Enhanced Metadata](https://docs.massivemusic.com/docs/understanding-enhanced-metadata.md)
- [Artwork](https://docs.massivemusic.com/docs/artwork.md)
- [Frequently Asked Questions](https://docs.massivemusic.com/docs/faq.md)
- [Supported Formats](https://docs.massivemusic.com/docs/supported-formats.md)
- [Supported Licensors](https://docs.massivemusic.com/docs/licensor-table.md)
- [Standard SLA](https://docs.massivemusic.com/docs/sla.md)
- [Fingerprinting](https://docs.massivemusic.com/docs/fingerprinting.md)
- [DMCA Radio Licensing Overview](https://docs.massivemusic.com/docs/dmca-radio-licensing-overview.md)
- [Encryption of cached media](https://docs.massivemusic.com/docs/encryption-of-cached-media.md)
- [Preview clip service](https://docs.massivemusic.com/docs/compliance-preview-clips.md)
- [Download service](https://docs.massivemusic.com/docs/compliance-download.md)
- [Catalogue streaming service](https://docs.massivemusic.com/docs/compliance-catalogue.md)
- [Subscription streaming service](https://docs.massivemusic.com/docs/compliance-subscription.md)
- [Postman Public Workspace](https://docs.massivemusic.com/docs/postman-sample-requests.md)
- [ETags](https://docs.massivemusic.com/docs/etags.md)
- [Client Usage Report](https://docs.massivemusic.com/docs/client-usage-reports-1.md)
- [Label Reports](https://docs.massivemusic.com/docs/label-reports.md)
- [Compliance Testing](https://docs.massivemusic.com/docs/testing-logs.md)
- [File Transfers](https://docs.massivemusic.com/docs/file-transfers.md)
- [Popularity Reports Delivery](https://docs.massivemusic.com/docs/popularity-reports-delivery.md): Set up delivery for twice-weekly popularity reports that rank tracks, artists, and products across the MassiveMusic global catalogue.
- [S3 Bucket Logging](https://docs.massivemusic.com/docs/s3-bucket-logging.md)
- [Catalogue Streaming plays S3 bucket logger](https://docs.massivemusic.com/docs/streaming-plays-s3-bucket-logger.md)
- [Subscription plays S3 bucket logger](https://docs.massivemusic.com/docs/subscription-plays-s3-bucket-logger.md)
- [Preview clips S3 bucket logger](https://docs.massivemusic.com/docs/preview-clips-logger.md)
- [Implementation Guide Overview](https://docs.massivemusic.com/docs/implementation-guide-overview.md)
- [Testing Process for DDEX Delivery](https://docs.massivemusic.com/docs/testing-process-for-ddex-delivery.md)
- [Delivering Content to Our SFTP](https://docs.massivemusic.com/docs/delivering-content-to-our-sftp.md)
- [Guide to Content Delivery Specifications and Best Practices](https://docs.massivemusic.com/docs/guide-to-content-delivery-specifications-and-best-practices.md)
- [Non-DDEX Implementation Guide](https://docs.massivemusic.com/docs/non-ddex-implementation-guide.md)
- [Components of an ERN Message](https://docs.massivemusic.com/docs/ddex-ern-38.md)
- [Message Header and Footer](https://docs.massivemusic.com/docs/message-header-and-footer.md)
- [Resource List and Technical Details](https://docs.massivemusic.com/docs/resource-list-and-technical-details.md)
- [Technical Sound Recording details and Image](https://docs.massivemusic.com/docs/technical-sound-recording-details-and-image.md)
- [Release List](https://docs.massivemusic.com/docs/release-list.md)
- [Release Details by Territory](https://docs.massivemusic.com/docs/release-details-by-territory.md)
- [Streaming Availability](https://docs.massivemusic.com/docs/streaming-availability.md)
- [Download availability](https://docs.massivemusic.com/docs/download-availability.md)
- [Client Inclusion for Distribution Channels](https://docs.massivemusic.com/docs/client-inclusion-for-distribution-channels.md)
- [Health Dashboards](https://docs.massivemusic.com/docs/health-dashboards.md)
- [Support](https://docs.massivemusic.com/docs/support.md)
- [External Partner Network and Integrations](https://docs.massivemusic.com/docs/external-partner-network-and-integrations.md)
- [Our Partners](https://docs.massivemusic.com/docs/partners.md)
## API Reference
- [Introduction](https://docs.massivemusic.com/reference/introduction.md)
- [Authentication](https://docs.massivemusic.com/reference/authentication.md)
- [Request format](https://docs.massivemusic.com/reference/request-format.md)
- [Error responses](https://docs.massivemusic.com/reference/error-responses.md): Identify API error codes, inspect error payloads, and handle batch request failures.
- [Usage limits](https://docs.massivemusic.com/reference/usage-limits.md): Understand daily request limits for non-live API keys and how to read rate-limit response headers.
- [Image sizes](https://docs.massivemusic.com/reference/image-sizes.md)
- [About the Catalogue API](https://docs.massivemusic.com/reference/about-this-api.md)
- [Search](https://docs.massivemusic.com/reference/search-1.md): Search the MassiveMusic catalogue for artists, releases, and tracks by query terms and filters, then use returned IDs in downstream workflows.
- [Track](https://docs.massivemusic.com/reference/track-search.md): Search the MassiveMusic catalogue for tracks matching the search query. Responses are weighted by popularity based on platform usage.
- [Release](https://docs.massivemusic.com/reference/release-search.md): Search the MassiveMusic catalogue for releases matching the search query. Responses are weighted by popularity based on platform usage.
- [Artist](https://docs.massivemusic.com/reference/artist-search.md): Search the MassiveMusic catalogue for artists matching the search query. Responses are weighted by popularity based on platform usage.
- [Artist](https://docs.massivemusic.com/reference/artist-1.md)
- [Details](https://docs.massivemusic.com/reference/details.md): Get all available artist details.
- [Releases](https://docs.massivemusic.com/reference/releases.md): Get a list of releases by given artist. Releases can be filtered by type.
- [Browse by name](https://docs.massivemusic.com/reference/browse-by-name.md): Get a list of artists from the 7digital catalogue whose names match the start letter(s) supplied.
- [Release](https://docs.massivemusic.com/reference/release-1.md)
- [Details](https://docs.massivemusic.com/reference/release-details.md): Get all available details for a given release.
- [Details in batch](https://docs.massivemusic.com/reference/details-in-batch.md): Get details of multiple releases in one request. In the request, releases are identified by release id. There will be one release in the response for every corresponding valid id in the request, and the releases will be in the same order as the requested ids. Releases that are not valid for any reason are omitted from the releases list in the response. They will be included in the errors list, in order, if showErrors is set true.
- [Track listing](https://docs.massivemusic.com/reference/track-listing.md): Get a list of all tracks constituting the release.
- [Track](https://docs.massivemusic.com/reference/track-1.md)
- [Details](https://docs.massivemusic.com/reference/track-details.md): Get all available details for a given track.
- [Details in batch](https://docs.massivemusic.com/reference/details-in-batch-1.md): Get details of multiple tracks in one request. In the request, tracks are identified by track id. There will be one track in the response for every corresponding valid id in the request, and the tracks will be in the same order as the requested ids. Tracks that are not valid for any reason are omitted from the tracks list in the response. They will be included in the errors list, in order, if showErrors is set true.
- [Usage type information](https://docs.massivemusic.com/reference/usage-type-information.md)
- [Download](https://docs.massivemusic.com/reference/download.md)
- [Streaming (HTTP Progressive)](https://docs.massivemusic.com/reference/streaming-http-progressive.md)
- [Subscription streaming (HTTP Progressive)](https://docs.massivemusic.com/reference/stream-to-subscriber.md): Stream any track available for streaming in the user's region, as long as they have a valid subscription.
This endpoint should only be used when a given device is actively connected to the Internet. For local caching in bulk, to be used for offline plays, see [Stream to subscriber - offline](ref:stream-to-subscriber-offline). Tracks can be cached (in an [encrypted format](https://docs.7digital.com/docs/encryption-of-cached-media)) on the end user's device, but all plays from either the cache or live must be reported with the [user/subscription/log](ref:report-a-subscriber-stream) endpoint.
When the clientId parameter is supplied, multiple devices will not be allowed to stream concurrently. Device A can start streaming, but if Device B starts, Device A will finish its current track then be blocked from playing again for a short time period. After that time period, Device A can play again, and Device B will become blocked.
 
- [Subscription streaming - offline (HTTP Progressive)](https://docs.massivemusic.com/reference/stream-to-subscriber-offline.md): This endpoint should only be used when a given device is actively connected to the Internet. For local caching in bulk, to be used for offline plays, see [Stream to subscriber - offline](ref:stream-to-subscriber-offline). Tracks can be cached (in an [encrypted format](https://docs.7digital.com/docs/encryption-of-cached-media)) on the end user's device, but all plays from either the cache or live must be reported with the [user/subscription/log](ref:report-a-subscriber-stream) endpoint.
When the clientId parameter is supplied, multiple devices will not be allowed to stream concurrently. Device A can start streaming, but if Device B starts, Device A will finish its current track then be blocked from playing again for a short time period. After that time period, Device A can play again, and Device B will become blocked.
 
- [Catalogue streaming (HTTP Progressive)](https://docs.massivemusic.com/reference/stream-any-track-radio-use.md): Stream any track in the MassiveMusic catalogue available in the user's region.
This endpoint is designed for non-subscription streaming plays where stream requests are not validated against an existing, valid subscription or an existing user account.
Tracks can be cached (in an encrypted format) on the end user's device, but all plays from either the cache or live must be reported with the [catalogue/log](ref:report-a-catalogue-stream) endpoint.
 
- [ALC locker streaming (HTTP Progressive)](https://docs.massivemusic.com/reference/stream-from-locker.md): Stream a previously purchased track from a user's locker. This endpoint can be used for online plays or offline caching (for plays when the device isn't connected to the Internet). Stream a previously purchased track from a user's locker. This endpoint can be used for online plays or offline caching (for plays when the device isn't connected to the Internet).   
- [Preview clip streaming (HTTP Progressive)](https://docs.massivemusic.com/reference/play-preview-clip.md): Stream a track preview clip from the MassiveMusic catalogue.
If authorisation is successful the bytes for the clip will be returned to the client. The request url should not be stored for reuse since it expires. All preview clip plays must be reported to the [preview/log](ref:report-a-preview-stream) endpoint.
 
- [Streaming (HLS)](https://docs.massivemusic.com/reference/streaming-hls.md)
- [Subscription streaming (HLS)](https://docs.massivemusic.com/reference/stream-to-subscriber-hls.md): Stream any track available for streaming in the user's region, as long as they have a valid subscription.
This endpoint should only be used when a given device is actively connected to the Internet. For local caching in bulk, to be used for offline plays, see [Stream to subscriber - offline](ref:stream-to-subscriber-offline-hls). All plays from either the cache or live must be reported with the [user/subscription/log](ref:report-a-subscriber-stream) endpoint.
When the clientId parameter is supplied, multiple devices will not be allowed to stream concurrently. Device A can start streaming, but if Device B starts, Device A will finish its current track then be blocked from playing again for a short time period. After that time period, Device A can play again, and Device B will become blocked.
 
- [Subscription streaming - offline (HLS)](https://docs.massivemusic.com/reference/stream-to-subscriber-offline-hls.md): Stream any track available for streaming in the user's region, as long as they have a valid subscription account already set up with our subscription system and their device is registered for offline play with the [user/unlimitedStreaming/offline](ref:authorise-device-for-off-line-streaming) endpoint.This endpoint should only be used when a given device is caching for offline track play (where it won't be connected to the Internet).All plays done during offline mode must be reported to the [user/subscription/log](ref:report-a-subscriber-stream) endpoint as soon as Internet connectivity is restored.
 
- [Catalogue streaming (HLS)](https://docs.massivemusic.com/reference/stream-to-radio-user-hls.md): Stream any track in the MassiveMusic catalogue available in the user's region.
This endpoint is designed for non-subscription streaming plays where stream requests are not validated against an existing, valid subscription or an existing user account.
Tracks can be cached (in an encrypted format) on the end user's device, but all plays from either the cache or live must be reported with the [catalogue/log](ref:report-a-catalogue-stream) endpoint.
 
- [ALC locker streaming (HLS)](https://docs.massivemusic.com/reference/stream-from-locker-hls.md): Stream a previously purchased track from a user's locker. This endpoint can be used for online plays or offline caching (for plays when the device isn't connected to the Internet)
 
- [Authorise device for off-line streaming](https://docs.massivemusic.com/reference/authorise-device-for-off-line-streaming.md): Authorise a device for offline mode. The POST body can be sent in either JSON or XML formats.  
- [Device status for off-line streaming](https://docs.massivemusic.com/reference/device-status-for-off-line-streaming.md): Get the offline status of a specified device. This status can be changed with a POST to the user/unlimitedStreaming/offline endpoint.  
- [Devices authorised for off-line streaming](https://docs.massivemusic.com/reference/devices-authorised-for-off-line-streaming.md): Get a list of all of the user's registered devices.  
- [Download Purchases](https://docs.massivemusic.com/reference/download-1.md)
- [Download purchased track](https://docs.massivemusic.com/reference/download-track.md): Download a purchased track.  
- [Download purchased release](https://docs.massivemusic.com/reference/download-release-zip.md): Download tracks in a purchased release as a single ZIP file.  
- [Download purchase](https://docs.massivemusic.com/reference/download-purchase-zip.md): Download tracks purchased in a transaction as a single ZIP file. The highest quality available for each track will be used.  
- [Media Transfer](https://docs.massivemusic.com/reference/transfer-media-files-for-content-delivery.md): Retrieve media files of any track. It allows the download of an entire licensed catalogue in any supported format or bitrate. Use of this endpoint is likely to necessitate additional technical due diligence on the part of the licensors and partner. **Acceptable usage** for this endpoint is considered to be 50 requests per second. Usage of this endpoint should be coordinated with your Client Success manager. 
- [About the Logging API](https://docs.massivemusic.com/reference/about-the-logging-api.md)
- [Report a subscriber stream](https://docs.massivemusic.com/reference/report-a-subscriber-stream.md): Report a track that has been streamed by a user which had a subscription. It is recommended to log streams in near real-time, or the same day in batches of 10-20 logs per request. Before logging actual user data, your Client Success Manager will support you through Compliance Testing to ensure logging accuracy and usage of the appropriate endpoint.  
- [Report a catalogue stream](https://docs.massivemusic.com/reference/report-a-catalogue-stream.md): Report a track that has been streamed to a user who was listening in a radio style playback. It is recommended to log streams in near real time, or the same day in batch. Before logging actual user data, your Client Success manager will support you through Compliance Testing to ensure logging accuracy and usage of the appropriate endpoint.  
- [Report a preview stream](https://docs.massivemusic.com/reference/report-a-preview-stream.md): Report a preview clip that has been played.**Acceptable usage** for this endpoint is 5 POST requests per second, and with batches of 500 logs per request. If you are likely to exceed this usage limit, MassiveMusic supports bulk batch submission of logs via an S3 bucket. This solution can be discussed this with your Client Success representative.
- [Create playlist](https://docs.massivemusic.com/reference/create-playlist.md): Create a new playlist tied to your partner consumer key. Playlists can be associated with the partner or a specific user, by setting the userId query parameter. When creating a new playlist you can provide an initial track listing in the request or create an empty playlists by leaving the "tracks" array empty. When adding a track to a playlist there are certain properties you can optionally specify, see playlists/{playlistId}/tracks for details The POST body parameters should be formatted as raw JSON.  
- [List playlists](https://docs.massivemusic.com/reference/list-playlists.md): Get a list of the partner's playlists. 
- [Update playlist details](https://docs.massivemusic.com/reference/update-playlist-details.md): Update a playlist details at {playlistId} with the supplied playlist details. It does not affect playlist tracks. Use this method e.g. for changing visibility of the playlist from private to public. Descriptions are limited to 500 characters. Descriptions over this length are truncated. 
- [Add tracks to playlist](https://docs.massivemusic.com/reference/add-tracks-to-playlist.md): Add an array of tracks to the playlist at {playlistId}. All metadata (e.g. track title, artist, etc) for tracks needs to be provided in the API call. The "source" property is optional, and defaults to 7digital. This relates to the audioUrl and image response and can be used to indicate a different source for the physical file, it can be any string you want as long as the application you use to add the track can understand it.The "audioUrl" property is optional and allows you to specify a different source for the physical file e.g. source="local" and audioUrl="file://a.specific.file.location.mp3" could mean that the consuming application understands how to handle a file stored at the given audioUrl.It is advisable that you only use these extra parameters if you need to use them. It's also advisable if you are accessing public playlists that some tracks may not be playable by your application, so we would advise including an option to hide, grey out non source=7digital tracks.
- [About the Interactive Radio API](https://docs.massivemusic.com/reference/about-the-interactive-radio-api.md)
- [Create a Listening Session](https://docs.massivemusic.com/reference/create-an-interactive-radio-session.md): Create an Interactive Radio session (listening session) from one or more playlists that you have created on the MassiveMusic platform ([via the Playlist API](ref:about-the-playlist-api) or [Playlist Tool)](doc:using-the-7digital-playlist-tool))A listening session is required per user, each time they launch a station. This listening session will help determine which tracks can be played and keep track of the number of skips that are permitted in line with the ruleset that your service operates within.
- [Delete a Listening Session](https://docs.massivemusic.com/reference/delete-an-interactive-radio-session.md): Delete an active listening session.
- [Get the next track](https://docs.massivemusic.com/reference/get-the-next-track.md): Get the next track which can be played within the listening session.The next track will be calculated based on the ruleset which your service follows (eg. DMCA, configured by MassiveMusic upon service setup).
- [Track Playback Events](https://docs.massivemusic.com/reference/track-playback-events.md): In order to comply with the specific Interactive Radio rulesets (eg. DMCA, GVL), you are required to send back each user's playback events. These events will directly influence the tracks are allowed to be played and skipped in the current listening session.
- [About the User Management API](https://docs.massivemusic.com/reference/about-the-user-management-api.md)
- [Create a new user](https://docs.massivemusic.com/reference/create-a-new-partner-user.md): Create a new user account. The OAuth 1.0 signature base string includes the parameters from the request entity-body if the body is single-part and `application/x-www-form-urlencoded`. For example, a JSON body should not be included in the base string. Reference: [here](https://www.rfc-editor.org/rfc/rfc5849#section-3.4.1) 
- [About the Subscriptions API](https://docs.massivemusic.com/reference/about-the-subscriptions-api.md)
- [Create a subscription](https://docs.massivemusic.com/reference/create-a-subscription.md): Create a user's subscription.You must notify us of new subscriptions. This is essential in granting streaming access for any given user, and in royalty and usage reporting back to the licensors.Subscriptions last for a maximum of a month, and must be renewed by the client if the user remains subscribed to the service for a longer duration. The OAuth 1.0 signature base string includes the parameters from the request entity-body when the body is single-part and `application/x-www-form-urlencoded`. Reference: [here](https://www.rfc-editor.org/rfc/rfc5849#section-3.4.1) 
- [Credit item](https://docs.massivemusic.com/reference/credit-item.md): Log a sale of a track or release for the specified user and add that track or release to the user's locker. You're free to retail in whichever currency suits you best, but you must ensure you log back in the currency which we provided to you for that piece of content. ie, if we provide a USD RRP to you in a non-US country and you decide to retail the product in local currency, you must log back the sale specifying USD as the currency.Please note, this endpoint exclusively supports XML responses and does not return data in other formats such as JSON.
 
- [User's locker](https://docs.massivemusic.com/reference/users-locker.md): The locker allows you to manage an individual user's purchased tracks and releases.Get a paged list of releases and tracks for a user's locker (collection of all purchased tracks).
 
- [Report release refund](https://docs.massivemusic.com/reference/report-release-refund.md): Remove a purchase of a release from the sales report when the purchase has been refunded. 
- [Report track refund](https://docs.massivemusic.com/reference/report-track-refund.md): Remove a purchase of a track from the sales report when the purchase has been refunded. 
## Pages
- [Incident Escalation](https://docs.massivemusic.com/incident-escalation.md)
- [Warner Music Group Integration Steps](https://docs.massivemusic.com/umg-integration-steps.md)
- [Universal Music Group - Security Due Diligence](https://docs.massivemusic.com/umg-security-due-diligence.md)
## Changelog
- [Handling Track and Release Download Availability](https://docs.massivemusic.com/changelog/handling-track-and-release-download-availability.md)
- [Removed reference to deprecated products + Added takedown clarification](https://docs.massivemusic.com/changelog/removed-reference-to-deprecated-products-added-takedown-clarification.md)
- [ClipStartPoint - Events Schema and Example](https://docs.massivemusic.com/changelog/clipstartpoint-events-schema-and-example.md)
- [Adding Clip Start Point to Events](https://docs.massivemusic.com/changelog/adding-clip-start-point-to-events.md)
- [GZipping/Compressing Events Messages](https://docs.massivemusic.com/changelog/gzippingcompressing-events-messages.md)