Catalogue Feed (CF)

Catalogue Feed is a standalone product for running your own music service on top of the fully licensed catalogue managed by Tuned Global. Tuned Global ingests, standardises, and enriches the catalogue metadata and stores the audio and artwork. You build the apps, search, playlisting, and user accounts your listeners actually see. It is the foundation layer, not the finished experience.

This is a different model from the ​Advanced APIs​, which power a ready-made listening experience you integrate against. With Catalogue Feed you own the platform and Tuned Global supplies the catalogue underneath it, delivered as a bulk metadata feed plus a single API integration for assets, search, and reporting.

Catalogue Feed or Advanced APIs

Both give you the same catalogue. They differ in how much of the platform you build yourself.

If you would rather Tuned Global manage everything for you, the Advanced API is the alternative. Your account executive can help you choose.

How the integration works

The lifecycle is a loop: ingest the catalogue once, keep it in sync, deliver assets as listeners play them, and report those plays back.

• Set up the feed​ once. Tuned Global writes your catalogue JSON to a Tuned Global S3 bucket, your own S3 bucket, or your SFTP server.
• Ingest the metadata​ into your systems, applying territory, platform, and label rights as you go.
• Deliver assets on demand​ by calling the stream and image endpoints when a listener requests a track or artwork.
• Log every play​ so Tuned Global can produce end-of-month reports for rights holders.

You choose how much you host yourself, from mirroring the entire catalogue including audio, down to holding metadata only and streaming everything else on demand. The three integration models are covered in Getting started.

Platform capabilities

The catalogue feed

• A bulk JSON metadata feed delivered to S3 or SFTP, configured once
• A full feed for the initial load, then incremental deltas (creates, updates, and deletes) for ongoing synchronisation
• A downloadable sample catalogue for evaluation, with no feed setup required

Catalogue data and sync

• Pull your assigned catalogue (your shelf) and page through it at ingestion scale
• Fetch only what has changed since your last request, and mark records as downloaded to track sync state
• Retrieve full detail for albums, tracks, and songs, including their contributors
• Look up the metadata for an individual song
• Resolve duplicate recordings with track disambiguation, looked up by track ID or ISRC

Asset delivery

• Stream audio on demand, with each stream recorded as a billable fetch
• Retrieve short preview clips for a track
• Retrieve artwork, resized on the fly by the Image Engine to whatever dimensions your application needs

Catalogue search

• Search the master catalogue by song, album, and label
• Built for matching, deduplication, and validation inside an ingestion pipeline, rather than end-user search
• For listener-facing search, use the Search capability in the Advanced APIs

Content control

• Maintain a per-store allowlist of songs to enforce rights and availability
• Add, check, and remove individual songs, or bulk-upload an allowlist from a spreadsheet

Play logging

• Report a single play with log play, or many at once with log batch play
• Drives label reporting and royalty accounting
• Separate from the fetch logs generated automatically on every audio stream, which drive your monthly billing. Both are required: the fetch log alone is not sufficient for label reporting

Built as a single delivery API

Everything except the bulk feed is served by one versioned delivery API (v5) at ​api-delivery-connect.tunedglobal.com​. Every request carries your ​StoreId​ and a ​Country​. Authentication uses your partner access key and secret key: catalogue and asset reads are signed with HMAC, while play logging and bulk uploads use HTTP Basic. The Authentication section covers the scheme each endpoint uses.

Because the delivery API is built for server-side ingestion rather than per-user sessions, there is no end-user login or token in this product. You authenticate as the platform, and your platform authenticates your listeners.