Tuned Global

Getting Started

This API provides READ access to public information content.

API Reference

Authentication

API Key Authentication

Basic HTTP Authentication

HMAC Authentication

Search

Album Search

Song Search

Catalogue

Retrieve Tracks for an Album

Retrieve Song detail

Upload Allowed Songs

Get Assets

Retrieve the image URL for album/track

Retrieve stream URL for a track

Retrieve preview URL for a track

Log Plays

Log a play for the specified track

Log plays in batches

CDS Metadata Feed

JSON Specification

JSON Example

TunedGlobal.API.Delivery Version 4

Catalogue Delivery Service

Production

<p class="slate-p " ></p><h2 class="slate-h2 " >Catalogue Delivery Service (CDS)</h2><div style="text-align:left"><figure ><div style="display:inline-block"><img src="https://theneo-prod-public.s3.amazonaws.com/images-1690258627277.jpg" alt="" style="
              width:800px;
	            height:590px;
	            aspect-ratio:800 / 590"
         /></div></figure></div><h2 class="slate-h2 " >What is a Catalogue Delivery Service?</h2><p class="slate-p " >A Catalogue Delivery Service (CDS) is used where a client wishes to store the catalogue metadata, and in some cases assets, on their own system.  This would mean that the client is building out all or most APIs that would be required for their particular use case.  In each use case below the client can send logging information to enable Tuned to complete end of month rights holders reporting, subject to this being included in your agreement.  At a high level, the types of use cases are:</p><ol class="slate-ol " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Where the client wishes to store and deliver all metadata to end users, including images and audio.  </strong>
The client will use the <a href="652fa743d08d00bb91795ae7" target="">CDS JSON metadata feed</a> to access all metadata and then use the images and assets APIs to retrieve audio and images, all of these items shall be stored by the client.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Where the client wishes to store and deliver all metadata to end users, </strong><span style="color:#FE0000"><strong class="slate-bold">including images but all audio would be delivered by the Tuned Global systems.</strong></span>
The client will use the <a href="652fa743d08d00bb91795ae7" target="">CDS JSON metadata feed</a> to access all metadata and then use the images APIs to retrieve images, these items shall be stored by the client.  Audio assets will only be fetched using the APIs as they are requested by users.  This should mean considerable savings by the client as large sized audio assets will not need to be stored and only accessed on demand.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Where the client wishes to store and deliver all metadata to end users, </strong><span style="color:#FE0000"><strong class="slate-bold">but all images and audio would be delivered by the Tuned Global systems.</strong></span>
The client will use the <a href="652fa743d08d00bb91795ae7" target="">CDS JSON metadata</a> feed to access all metadata which shall be stored by the client.  Audio assets and Image assets will only be fetched using the APIs as they are requested by users.  This should mean considerable savings by the client as large sized audio assets will not need to be stored and only accessed on demand while images can be available at eny size required by the client applications.</div></li></ol><p class="slate-p " ></p><div style="width:100%;
	min-width:100%;" class="callout-widget" data-type=success ><div class="callout-icon"><svg width="18" height="18" viewBox="0 0 18 18" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M7.77116 10.8968L5.72949 8.8551C5.60449 8.7301 5.45171 8.6676 5.27116 8.6676C5.0906 8.6676 4.93088 8.73705 4.79199 8.87594C4.6531 9.01482 4.58366 9.17455 4.58366 9.3551C4.58366 9.53566 4.6531 9.68844 4.79199 9.81344L7.33366 12.3551C7.45866 12.4801 7.60449 12.5426 7.77116 12.5426C7.93783 12.5426 8.08366 12.4801 8.20866 12.3551L13.2087 7.3551C13.3337 7.2301 13.3927 7.07732 13.3857 6.89677C13.3788 6.71621 13.3128 6.56344 13.1878 6.43844C13.0628 6.29955 12.9066 6.2301 12.7191 6.2301C12.5316 6.2301 12.3684 6.29955 12.2295 6.43844L7.77116 10.8968ZM9.00033 17.3343C7.81977 17.3343 6.72255 17.1225 5.70866 16.6989C4.69477 16.2752 3.81283 15.6884 3.06283 14.9384C2.31283 14.1884 1.72602 13.3065 1.30241 12.2926C0.878798 11.2787 0.666992 10.1815 0.666992 9.00094C0.666992 7.83427 0.878798 6.74399 1.30241 5.7301C1.72602 4.71621 2.31283 3.83427 3.06283 3.08427C3.81283 2.33427 4.69477 1.74399 5.70866 1.31344C6.72255 0.88288 7.81977 0.667603 9.00033 0.667603C10.167 0.667603 11.2573 0.88288 12.2712 1.31344C13.285 1.74399 14.167 2.33427 14.917 3.08427C15.667 3.83427 16.2573 4.71621 16.6878 5.7301C17.1184 6.74399 17.3337 7.83427 17.3337 9.00094C17.3337 10.1815 17.1184 11.2787 16.6878 12.2926C16.2573 13.3065 15.667 14.1884 14.917 14.9384C14.167 15.6884 13.285 16.2752 12.2712 16.6989C11.2573 17.1225 10.167 17.3343 9.00033 17.3343ZM9.00033 16.0843C11.0142 16.0843 12.6982 15.4072 14.0524 14.053C15.4066 12.6989 16.0837 11.0148 16.0837 9.00094C16.0837 6.98705 15.4066 5.30302 14.0524 3.94885C12.6982 2.59469 11.0142 1.9176 9.00033 1.9176C6.98644 1.9176 5.30241 2.59469 3.94824 3.94885C2.59408 5.30302 1.91699 6.98705 1.91699 9.00094C1.91699 11.0148 2.59408 12.6989 3.94824 14.053C5.30241 15.4072 6.98644 16.0843 9.00033 16.0843Z" fill="#06837A"></path></svg></div><div ><p class="slate-p " >Where a client prefers to not manage any APIs or metadata, Tuned Global has an Advanced API (aAPI) solution that manages these requirements.  Please discuss this requirement directly with your Tuned Global account executive.</p></div></div><div class="slate-hr"><hr contenteditable="false" class="slate-HrElement-hr"/></div><p class="slate-p " >The components of a Catalogue Delivery Service are;</p><ol class="slate-ol " ><li class="slate-li " ><div style="position:relative">A JSON Feed that contains metadata you require, plus</div></li><li class="slate-li " ><div style="position:relative">A set of APIs that allow you to get the assets you may need</div></li><li class="slate-li " ><div style="position:relative">A set of reporting APIs </div></li><li class="slate-li " ><div style="position:relative">A general set of APIs to manage some components of the service.</div></li></ol><div class="slate-hr"><hr contenteditable="false" class="slate-HrElement-hr"/></div><p class="slate-p " >To implement this service we would recommend that you first implement in the following order;</p><ol class="slate-ol " ><li class="slate-li " ><div style="position:relative">The importing and management of the JSON feed.  Read the Catalogue Delivery Service documentation.</div></li><li class="slate-li " ><div style="position:relative">Retrieving image assets and using the image resizing engine if required</div></li><li class="slate-li " ><div style="position:relative">Retrieving preview assets (where required and available)</div></li><li class="slate-li " ><div style="position:relative">Retrieving full length audio assets (where required and available)</div></li><li class="slate-li " ><div style="position:relative">Where Tuned is managing reporting, implement the logging of plays as per the specification</div></li></ol><p class="slate-p " ></p><p class="slate-p " ></p>

A Catalogue Delivery Service (CDS) is used where a client wishes to store the catalogue metadata, and in some cases assets, on their own system.  This would mean that the client is building out all or most APIs that would be required for their particular use case.  In each use case below the client can send logging information to enable Tuned to complete end of month rights holders reporting, subject to this being included in your agreement.  At a high level, the types of use cases are:

The components of a Catalogue Delivery Service are;

To implement this service we would recommend that you first implement in the following order;

<p class="slate-p " >This API provides READ access to public information content.</p><p class="slate-p " ><span style="background-color:transparent;color:rgb(0, 0, 0)">Tuned Global APIs are RESTful APIs available via the https protocol with documentation available via a Swagger interface.  The APIs are self documented and provide information on input parameters and return models.  API responses are available as XML or JSON.
This </span>documentation<span style="background-color:transparent;color:rgb(0, 0, 0)"> is an overview of the Swagger interface with additional context on usage.</span></p><p class="slate-p " ></p><div style="width:100%;
	min-width:100%;" class="callout-widget" data-type=error ><div class="callout-icon"><svg width="18" height="18" viewBox="0 0 18 18" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M9.08366 9.9801C9.25033 9.9801 9.39269 9.92107 9.51074 9.80302C9.6288 9.68496 9.68783 9.53566 9.68783 9.3551V5.31344C9.68783 5.14677 9.62533 5.00441 9.50033 4.88635C9.37533 4.7683 9.22949 4.70927 9.06283 4.70927C8.88227 4.70927 8.73296 4.7683 8.61491 4.88635C8.49685 5.00441 8.43783 5.15371 8.43783 5.33427V9.37594C8.43783 9.5426 8.50033 9.68496 8.62533 9.80302C8.75033 9.92107 8.9031 9.9801 9.08366 9.9801ZM9.00033 13.1676C9.19477 13.1676 9.35796 13.1016 9.48991 12.9697C9.62185 12.8377 9.68783 12.6745 9.68783 12.4801C9.68783 12.2857 9.62185 12.1225 9.48991 11.9905C9.35796 11.8586 9.19477 11.7926 9.00033 11.7926C8.80588 11.7926 8.64269 11.8586 8.51074 11.9905C8.3788 12.1225 8.31283 12.2857 8.31283 12.4801C8.31283 12.6745 8.3788 12.8377 8.51074 12.9697C8.64269 13.1016 8.80588 13.1676 9.00033 13.1676ZM9.00033 17.3343C7.81977 17.3343 6.72255 17.1225 5.70866 16.6989C4.69477 16.2752 3.81283 15.6884 3.06283 14.9384C2.31283 14.1884 1.72602 13.3065 1.30241 12.2926C0.878798 11.2787 0.666992 10.1815 0.666992 9.00094C0.666992 7.83427 0.878798 6.74399 1.30241 5.7301C1.72602 4.71621 2.31283 3.83427 3.06283 3.08427C3.81283 2.33427 4.69477 1.74399 5.70866 1.31344C6.72255 0.88288 7.81977 0.667603 9.00033 0.667603C10.167 0.667603 11.2573 0.88288 12.2712 1.31344C13.285 1.74399 14.167 2.33427 14.917 3.08427C15.667 3.83427 16.2573 4.71621 16.6878 5.7301C17.1184 6.74399 17.3337 7.83427 17.3337 9.00094C17.3337 10.1815 17.1184 11.2787 16.6878 12.2926C16.2573 13.3065 15.667 14.1884 14.917 14.9384C14.167 15.6884 13.285 16.2752 12.2712 16.6989C11.2573 17.1225 10.167 17.3343 9.00033 17.3343ZM9.00033 16.0843C10.9448 16.0843 12.6114 15.3898 14.0003 14.0009C15.3892 12.612 16.0837 10.9454 16.0837 9.00094C16.0837 7.05649 15.3892 5.38982 14.0003 4.00094C12.6114 2.61205 10.9448 1.9176 9.00033 1.9176C7.05588 1.9176 5.38921 2.61205 4.00033 4.00094C2.61144 5.38982 1.91699 7.05649 1.91699 9.00094C1.91699 10.9454 2.61144 12.612 4.00033 14.0009C5.38921 15.3898 7.05588 16.0843 9.00033 16.0843Z" fill="#E90005"></path></svg></div><div ><p class="slate-p " >Unless explicitly stated in either your direct licensor agreements or your Tuned Global agreements, Tuned Global catalogue, being either the assets or metadata, cannot be used to train Machine Learning or AI models.</p></div></div><p class="slate-p " ><span style="background-color:transparent;color:rgb(0, 0, 0)">
</span></p><div style="width:100%;
	min-width:100%;" class="callout-widget" data-type=info ><div class="callout-icon"><svg width="20" height="20" viewBox="0 0 20 20" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M10.0628 14.1676C10.2434 14.1676 10.3927 14.1086 10.5107 13.9905C10.6288 13.8725 10.6878 13.7232 10.6878 13.5426V9.77177C10.6878 9.6051 10.6253 9.46274 10.5003 9.34469C10.3753 9.22663 10.2295 9.1676 10.0628 9.1676C9.88227 9.1676 9.73296 9.22663 9.61491 9.34469C9.49685 9.46274 9.43783 9.61205 9.43783 9.7926V13.5634C9.43783 13.7301 9.50033 13.8725 9.62533 13.9905C9.75033 14.1086 9.89616 14.1676 10.0628 14.1676ZM10.0003 7.62594C10.1948 7.62594 10.358 7.56344 10.4899 7.43844C10.6219 7.31344 10.6878 7.15371 10.6878 6.95927C10.6878 6.76482 10.6219 6.59816 10.4899 6.45927C10.358 6.32038 10.1948 6.25094 10.0003 6.25094C9.80588 6.25094 9.64269 6.32038 9.51074 6.45927C9.3788 6.59816 9.31283 6.76482 9.31283 6.95927C9.31283 7.15371 9.3788 7.31344 9.51074 7.43844C9.64269 7.56344 9.80588 7.62594 10.0003 7.62594ZM10.0003 18.3343C8.81977 18.3343 7.72255 18.1225 6.70866 17.6989C5.69477 17.2752 4.81283 16.6884 4.06283 15.9384C3.31283 15.1884 2.72602 14.3065 2.30241 13.2926C1.8788 12.2787 1.66699 11.1815 1.66699 10.0009C1.66699 8.83427 1.8788 7.74399 2.30241 6.7301C2.72602 5.71621 3.31283 4.83427 4.06283 4.08427C4.81283 3.33427 5.69477 2.74399 6.70866 2.31344C7.72255 1.88288 8.81977 1.6676 10.0003 1.6676C11.167 1.6676 12.2573 1.88288 13.2712 2.31344C14.285 2.74399 15.167 3.33427 15.917 4.08427C16.667 4.83427 17.2573 5.71621 17.6878 6.7301C18.1184 7.74399 18.3337 8.83427 18.3337 10.0009C18.3337 11.1815 18.1184 12.2787 17.6878 13.2926C17.2573 14.3065 16.667 15.1884 15.917 15.9384C15.167 16.6884 14.285 17.2752 13.2712 17.6989C12.2573 18.1225 11.167 18.3343 10.0003 18.3343ZM10.0003 17.0843C11.9448 17.0843 13.6114 16.3898 15.0003 15.0009C16.3892 13.612 17.0837 11.9454 17.0837 10.0009C17.0837 8.05649 16.3892 6.38982 15.0003 5.00094C13.6114 3.61205 11.9448 2.9176 10.0003 2.9176C8.05588 2.9176 6.38921 3.61205 5.00033 5.00094C3.61144 6.38982 2.91699 8.05649 2.91699 10.0009C2.91699 11.9454 3.61144 13.612 5.00033 15.0009C6.38921 16.3898 8.05588 17.0843 10.0003 17.0843Z" fill="#3960B4"></path></svg></div><div ><p class="slate-p " >Swagger Interface: https: <a href="https://api-delivery-connect.tunedglobal.com/swagger/ui/index" target="_self">https://api-delivery-connect.tunedglobal.com/swagger/ui/index</a></p><p class="slate-p " ><strong class="slate-bold">Note:  Select Version 5 from dropdown on Swagger interface</strong></p></div></div><p class="slate-p " ><span style="background-color:transparent;color:rgb(0, 0, 0)">This </span>documentation<span style="background-color:transparent;color:rgb(0, 0, 0)"> pertains only to the V5 Content Delivery API.  It assumes that you receive a</span><a href="https://app.theneo.io/tuned-global/content-delivery/content-delivery-service/" target="_self"><span style="background-color:transparent;color:rgb(0, 0, 0)"> catalogue metadata feed</span></a><span style="background-color:transparent;color:rgb(0, 0, 0)"> from Tuned Global and use this data in your system.  This API requires that you use the product IDs in your catalogue feed to access assets for these products.</span></p>

Tuned Global APIs are RESTful APIs available via the https protocol with documentation available via a Swagger interface.  The APIs are self documented and provide information on input parameters and return models.  API responses are available as XML or JSON.
This 

 is an overview of the Swagger interface with additional context on usage.

 pertains only to the V5 Content Delivery API.  It assumes that you receive a

 from Tuned Global and use this data in your system.  This API requires that you use the product IDs in your catalogue feed to access assets for these products.

<p class="slate-p " >This section outlines the essential aspects of authenticating your requests to access our API services securely. Authentication is a crucial step in ensuring that only authorized users and applications can interact with our APIs, protecting sensitive data and maintaining the integrity of our services.</p><h2 class="slate-h2 " ><span style="color:#666666">Types of Authentication</span></h2><p class="slate-p " >We offer different authentication methods to suit diverse use cases and requirements. The most common authentication mechanisms supported by our APIs are:</p><ol class="slate-ol " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">API Key Authentication</strong>: This method involves including a unique API key with each request under a specific Http header. The API key acts as a simple yet effective way to identify and authorize applications or users.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Basic HTTP Authentication: </strong>Basic HTTP Authentication is a widely-used, simple, and stateless authentication method. It involves including the username and password in the request&apos;s &quot;Authorization&quot; header encoded in Base64 format. It is essential to use this method only over secure connections (HTTPS) to prevent credentials from being transmitted in plaintext.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">HMAC Authentication: </strong>HMAC (Hash-based Message Authentication Code) is a more advanced authentication method that ensures both integrity and authenticity of API requests. It involves generating a cryptographic hash using secret keys and the request data, which is then sent along with the request. The server verifies the hash to authenticate the request and detect any tampering.</div></li></ol><h2 class="slate-h2 " ><span style="color:#666666">
Getting Started with Authentication</span></h2><p class="slate-p " >To start using the API and benefit from its functionality, clients will need to obtain the necessary authentication credentials from Tuned Global. The process typically involves registering for an API key, obtaining the required username and password for Basic HTTP Authentication, or to be able to generate the HMAC credentials, depending on the authentication method you choose.</p><p class="slate-p " >In the following sub sections, we&apos;ll provide step-by-step guides and code examples for each authentication type to help you seamlessly integrate authentication into your applications.</p>

This section outlines the essential aspects of authenticating your requests to access our API services securely. Authentication is a crucial step in ensuring that only authorized users and applications can interact with our APIs, protecting sensitive data and maintaining the integrity of our services.

We offer different authentication methods to suit diverse use cases and requirements. The most common authentication mechanisms supported by our APIs are:

To start using the API and benefit from its functionality, clients will need to obtain the necessary authentication credentials from Tuned Global. The process typically involves registering for an API key, obtaining the required username and password for Basic HTTP Authentication, or to be able to generate the HMAC credentials, depending on the authentication method you choose.

In the following sub sections, we'll provide step-by-step guides and code examples for each authentication type to help you seamlessly integrate authentication into your applications.

<p class="slate-p " >Welcome to the Search API section of our comprehensive API documentation, where you gain access to an array of powerful search capabilities to traverse our extensive catalogue (restricted to what you have licensed). The Search API empowers developers like you to seamlessly integrate and leverage our vast collection, enabling efficient retrieval of the relevant content.</p><p class="slate-p " >Integrating our Search API into your applications is a streamlined process with developer-friendly API endpoints. Our documentation provides comprehensive insights into request structures, query parameters, and response formats, ensuring a seamless integration experience.</p><p class="slate-p " ></p><h3 class="slate-h3 " ><span style="color:#666666">Getting Started</span></h3><p class="slate-p " >To initiate your exploration of the master catalogue and harness the power of our Search API, please refer to the technical documentation below. Dive into the details of constructing search queries and leverage the full potential of our API to deliver personalized and compelling content experiences.</p><p class="slate-p " ></p><h3 class="slate-h3 " ><span style="color:#666666">Security Model</span></h3><p class="slate-p " >Search API uses the API Key security model. Please refer to the <a href="https://app.theneo.io/tuned-global/Content-Delivery/authentication/api-key-authentication" target="_self">API Key Authentication</a> section of the documentation for more details.</p>

Welcome to the Search API section of our comprehensive API documentation, where you gain access to an array of powerful search capabilities to traverse our extensive catalogue (restricted to what you have licensed). The Search API empowers developers like you to seamlessly integrate and leverage our vast collection, enabling efficient retrieval of the relevant content.

Integrating our Search API into your applications is a streamlined process with developer-friendly API endpoints. Our documentation provides comprehensive insights into request structures, query parameters, and response formats, ensuring a seamless integration experience.

To initiate your exploration of the master catalogue and harness the power of our Search API, please refer to the technical documentation below. Dive into the details of constructing search queries and leverage the full potential of our API to deliver personalized and compelling content experiences.

Search API uses the API Key security model. Please refer to the 

 section of the documentation for more details.

<p class="slate-p " >Welcome to the Catalogue API section of our API documentation. 

Use these APIs to view catalogue information or allow specific catalogue items into for your service.
</p><h3 class="slate-h3 " ><span style="color:#666666">Security Model</span></h3><p class="slate-p " >Catalogue Delivery Service APIs uses the API Key security model. Please refer to the <a href="https://app.theneo.io/tuned-global/Content-Delivery/authentication/api-key-authentication" target="_self">API Key Authentication</a> section of the documentation for more details.</p><p class="slate-p " ></p><p class="slate-p " ></p>

Welcome to the Catalogue API section of our API documentation. 

Use these APIs to view catalogue information or allow specific catalogue items into for your service.


Catalogue Delivery Service APIs uses the API Key security model. Please refer to the 

<p class="slate-p " >Welcome to the Assets API section of our comprehensive API documentation. This section showcases a set of powerful APIs that enable you to access and retrieve catalogue media  effortlessly. Use these APIs to access assets, being full length audio files, preview audio files or image URLs than can be used in conjunction with the Tuned Global image service.</p><h3 class="slate-h3 " ><span style="color:#666666">
Getting Started</span></h3><p class="slate-p " >To get started, simply choose the API that aligns with your requirements and follow the documentation provided below. Each API documentation includes endpoint details, parameters, and sample requests and responses to guide you through the integration process</p><h3 class="slate-h3 " ><span style="color:#666666">
Security Model</span></h3><p class="slate-p " >All Asset APIs use the HMAC security model. Please refer to the <a href="https://app.theneo.io/tuned-global/Content-Delivery/authentication/hmac-authentication" target="_self">HMAC </a>section of this documentation for more details.</p>

Welcome to the Assets API section of our comprehensive API documentation. This section showcases a set of powerful APIs that enable you to access and retrieve catalogue media  effortlessly. Use these APIs to access assets, being full length audio files, preview audio files or image URLs than can be used in conjunction with the Tuned Global image service.

To get started, simply choose the API that aligns with your requirements and follow the documentation provided below. Each API documentation includes endpoint details, parameters, and sample requests and responses to guide you through the integration process

All Asset APIs use the HMAC security model. Please refer to the 

section of this documentation for more details.

<p class="slate-p " >Welcome to the Log Play API section of our comprehensive API documentation. This section outlines the functionalities that allow you to efficiently log user plays to be able to generate the Label reports as well as music usage and user activity reports. 
<strong class="slate-bold">Note:</strong> This section is only applicable if Tuned Global is responsible for managing the internal and external (label) reports.</p><p class="slate-p " ></p><div style="width:100%;
	min-width:100%;" class="callout-widget" data-type=info ><div class="callout-icon"><svg width="20" height="20" viewBox="0 0 20 20" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M10.0628 14.1676C10.2434 14.1676 10.3927 14.1086 10.5107 13.9905C10.6288 13.8725 10.6878 13.7232 10.6878 13.5426V9.77177C10.6878 9.6051 10.6253 9.46274 10.5003 9.34469C10.3753 9.22663 10.2295 9.1676 10.0628 9.1676C9.88227 9.1676 9.73296 9.22663 9.61491 9.34469C9.49685 9.46274 9.43783 9.61205 9.43783 9.7926V13.5634C9.43783 13.7301 9.50033 13.8725 9.62533 13.9905C9.75033 14.1086 9.89616 14.1676 10.0628 14.1676ZM10.0003 7.62594C10.1948 7.62594 10.358 7.56344 10.4899 7.43844C10.6219 7.31344 10.6878 7.15371 10.6878 6.95927C10.6878 6.76482 10.6219 6.59816 10.4899 6.45927C10.358 6.32038 10.1948 6.25094 10.0003 6.25094C9.80588 6.25094 9.64269 6.32038 9.51074 6.45927C9.3788 6.59816 9.31283 6.76482 9.31283 6.95927C9.31283 7.15371 9.3788 7.31344 9.51074 7.43844C9.64269 7.56344 9.80588 7.62594 10.0003 7.62594ZM10.0003 18.3343C8.81977 18.3343 7.72255 18.1225 6.70866 17.6989C5.69477 17.2752 4.81283 16.6884 4.06283 15.9384C3.31283 15.1884 2.72602 14.3065 2.30241 13.2926C1.8788 12.2787 1.66699 11.1815 1.66699 10.0009C1.66699 8.83427 1.8788 7.74399 2.30241 6.7301C2.72602 5.71621 3.31283 4.83427 4.06283 4.08427C4.81283 3.33427 5.69477 2.74399 6.70866 2.31344C7.72255 1.88288 8.81977 1.6676 10.0003 1.6676C11.167 1.6676 12.2573 1.88288 13.2712 2.31344C14.285 2.74399 15.167 3.33427 15.917 4.08427C16.667 4.83427 17.2573 5.71621 17.6878 6.7301C18.1184 7.74399 18.3337 8.83427 18.3337 10.0009C18.3337 11.1815 18.1184 12.2787 17.6878 13.2926C17.2573 14.3065 16.667 15.1884 15.917 15.9384C15.167 16.6884 14.285 17.2752 13.2712 17.6989C12.2573 18.1225 11.167 18.3343 10.0003 18.3343ZM10.0003 17.0843C11.9448 17.0843 13.6114 16.3898 15.0003 15.0009C16.3892 13.612 17.0837 11.9454 17.0837 10.0009C17.0837 8.05649 16.3892 6.38982 15.0003 5.00094C13.6114 3.61205 11.9448 2.9176 10.0003 2.9176C8.05588 2.9176 6.38921 3.61205 5.00033 5.00094C3.61144 6.38982 2.91699 8.05649 2.91699 10.0009C2.91699 11.9454 3.61144 13.612 5.00033 15.0009C6.38921 16.3898 8.05588 17.0843 10.0003 17.0843Z" fill="#3960B4"></path></svg></div><div ><p class="slate-p " >For reporting purposes, it is necessary to log the 30 second point of play.  However we would suggest that best practice is to log Start of Play, 30 seconds, the Skip action (and the seconds at which this action occurs) and End of File.  This leads to better insights into the behaviour of your users and your application.</p></div></div><h3 class="slate-h3 " ><span style="color:#666666">Getting Started</span></h3><p class="slate-p " >To start logging plays and unlocking valuable analytics and insights into user behaviour and content performance, refer to the technical documentation below. Explore the play logging endpoints, understand the data format, and get started with implementing the Log Play APIs in your applications.</p><p class="slate-p " ></p><h3 class="slate-h3 " ><span style="color:#666666">Security Model</span></h3><p class="slate-p " >All Log Play APIs use the Basic HTTP Auth security model. Please refer to the  <a href="https://app.theneo.io/tuned-global/Content-Delivery/authentication/basic-http-authentication" target="_self">Basic HTTP Auth </a> section of this documentation for more details.</p><p class="slate-p " ></p><p class="slate-p " ></p>

Welcome to the Log Play API section of our comprehensive API documentation. This section outlines the functionalities that allow you to efficiently log user plays to be able to generate the Label reports as well as music usage and user activity reports. 


 This section is only applicable if Tuned Global is responsible for managing the internal and external (label) reports.

To start logging plays and unlocking valuable analytics and insights into user behaviour and content performance, refer to the technical documentation below. Explore the play logging endpoints, understand the data format, and get started with implementing the Log Play APIs in your applications.

All Log Play APIs use the Basic HTTP Auth security model. Please refer to the  

 section of this documentation for more details.

Tuned Global provides a metadata delivery feed as part of its Catalogue Delivery Specification.  Tuned Global accepts catalogue feeds from many labels in different formats.  Our ingestion program, Intaga, automatically processes these feeds and normalises the metadata structures. These Tuned Global metadata feeds enable clients to access this normalised structure and receive continuing updates of new products, changed products and takedowns.

You can use the information in these metadata feeds with the 

detailed here order to access assets.  These assets may be Album Artwork, Audio and Video files as per your license agreement.

The Tuned Global Catalogue Delivery Service provides a JSON formatted feed on a scheduled basis.  Once the initial feed has been provided, updates can be scheduled every hour, day or week - depending on your needs.  These feeds will be made available via an sFTP location that you can access OR an AWS S3 Bucket if you are currently an AWS user.

Note: If your S3 location is being used, these files will not be deleted and you will need to manage any delete policies within your AWS infrastructure.

The onboarding process will be as follows;

One of the most critical items to manage is the availability of a product, being an Album or a Track. Making a product available prior to its live date or not removing it after an end date is a significant breach of your licensing agreement and should be treated as a high level risk.

As a general overview the logic to manage rights and availability is:

The following provides instructions on when to make a track OR an album available to your audience. 
Only where there is a tick against all the elements should you make an album or track available.  Please keep in mind that rights to Albums and Tracks are distinct.

The below instructions depend on whether Tuned Global is providing Publishing data or not.

NOTE: REFERENCE TO NOT MAKING AN ALBUM OR TRACK AVAILABLE (LIVE) MEANS, ALL ASPECTS OF AN ALBUM AND OR TRACK. THIS INCLUDES PREVIEWS, ARTWORK, TITLES INCLUDING ALL METADATA.

Title

Album Notes: If no Tracks (below) have rights, you should not display the Album information as no tracks will be available to end users.

Album Notes: Publishing Data is only applicable at a track level.  If no Tracks (below) have both Master and Publishing rights for a territory, you should not display the Album information as no tracks will be available to end users

Sections