Handling Track and Release Download Availability
Clarification of how track download availability data is delivered via Catalogue Events has been added to the technical specifications page here.
Clarification of how track download availability data is delivered via Catalogue Events has been added to the technical specifications page here.
Removed reference to payments API and feeds from this page. Added clarification around takedown of streaming or download availability here.
As part of ongoing efforts to enhance our Catalogue Events product, we have introduced a new field, clipStartPoint. The start time specified in this field refers to the start point for the pre-transcoded preview clips that 7digital provides. We deployed the change today, on the 7th of May 2025. As a result, the provisional Events schema and example have been removed, and the full Events schema and example have been updated. You can find the updated schema and example here.
As part of improving our Catalogue Events product, we will be introducing clipStartPoint to track objects in the events schema. We plan to introduce this change during the week of the 5th May. A provisional schema has been made available in our documentation here.
We are now able to send Events messages compressed on a per-client basis. For current partners of ours interested in receiving gzipped messages, please contact your client success manager. For all new clients, Events messages will be automatically sent gzipped. More information can be found here .
Available Metadata page updated to include a description of normalised name and mapping of artists fields in Events vs the API/Feeds. Please see the updated page here.
Message below added to the Catalogue Events - Technical Specifications page here.
You may experience intermittent periods where no Events are received. This will likely be due to scheduled ingestion downtime. We will queue up and gradually process any pending messages within the same day if this needs to occur. If you have any questions or concerns, please reach out to your Client Success Manager.
We deployed a change to start storing and generating 1400px and 3000px when licensors send these sizes (or higher) to us. This is only for new content going forward. If higher-quality images are required, we may need licensors to re-deliver any images to us where available. You can find more information here.
As part of improving our Catalogue Events product, we have introduced normalisedName to artist objects in the events schema. We planned to deploy this change during the week of February 10th 2025 and deployed the change on the 11th of February. As a result, the provisional Events schema and example have been removed and the full Events schema and example have been updated. You can find the updated schema and example here.
Expectations around the handling of failed events messages have been clarified here.