Overview

The Tuned Global platform provides two interoperable integration models for accessing music, audio, and media content:

• API Suite​ – a unified application layer combining Metadata and Services APIs
• Catalogue Feed (CF / CDS)​ – a separate data distribution and ingestion interface

While these are presented within a single documentation structure, they serve different purposes and are accessed via ​separate API endpoints (Swagger definitions)​.

Tuned Global Platform
│
├── API Suite (Application Layer)
│ │
│ ├── Metadata API (Swagger)
│ │ └── Catalogue & Content
│ │ (Search, Artists, Albums, Tracks, Playlists,
│ │ Stations, Podcasts, Tags, CMS Content)
│ │
│ └── Services API (Swagger)
│ └── User & Playback Layer
│ (Users, Authentication, Profiles, Collections,
│ Playlists, Stations, Queue, Streaming,
│ Billing, Subscriptions, Activity & Logging)
│
└── Catalogue Feed (CDS) (Data / Ingestion Layer)
 │
 ├── Catalogue Feed API (Swagger)
 │ └── Operational Access
 │ (Search, Catalogue Lookup, Asset Delivery,
 │ Stream URLs, Image URLs, Play Logging)
 │
 └── Metadata Feed (JSON / Batch)
 └── Bulk Data Distribution
 (Full Catalogue Sync, Updates, Allow Lists)

→ API Suite and Catalogue Feed are independent but interoperable
→ Applications may use one or both depending on architecture Tuned Global Platform
│
├── API Suite (Application Layer)
│ │
│ ├── Metadata API (Swagger)
│ │ └── Catalogue & Content
│ │ (Search, Artists, Albums, Tracks, Playlists,
│ │ Stations, Podcasts, Tags, CMS Content)
│ │
│ └── Services API (Swagger)
│ └── User & Playback Layer
│ (Users, Authentication, Profiles, Collections,
│ Playlists, Stations, Queue, Streaming,
│ Billing, Subscriptions, Activity & Logging)
│
└── Catalogue Feed (CDS) (Data / Ingestion Layer)
 │
 ├── Catalogue Feed API (Swagger)
 │ └── Operational Access
 │ (Search, Catalogue Lookup, Asset Delivery,
 │ Stream URLs, Image URLs, Play Logging)
 │
 └── Metadata Feed (JSON / Batch)
 └── Bulk Data Distribution
 (Full Catalogue Sync, Updates, Allow Lists)

→ API Suite and Catalogue Feed are independent but interoperable
→ Applications may use one or both depending on architecture

1. API Suite

The API Suite is the primary interface for building user-facing applications. It combines two complementary API layers:

• Metadata APIs​ – provide catalogue and content data without user context
• Services APIs​ – provide user-specific functionality, playback, and transactional operations

Each layer is exposed via its own Swagger endpoint, but they are designed to be used together as a single logical system.

Using the API Suite, you can:

• Search and browse the catalogue (artists, albums, tracks, playlists, stations, podcasts, etc.)
• Retrieve structured metadata and editorial content
• Manage users, authentication, and profiles
• Enable playback, streaming, and queue management
• Build playlists, stations, and personalised listening experiences
• Manage collections, favourites, and social features
• Handle subscriptions, billing, and entitlements
• Track playback activity and analytics

In practice:

• Metadata APIs​ are used to build discovery and browsing experiences
• Services APIs​ extend those experiences with user context and interaction

2. Catalogue Feed (CF / CDS)

The Catalogue Feed provides a distinct integration model focused on ​catalogue access, synchronisation, and controlled delivery​.

It is exposed via its own Swagger endpoint and operates independently from the API Suite.

The Catalogue Feed is designed for:

• Ingesting and synchronising catalogue data into external systems
• Performing lightweight search and lookup operations
• Retrieving media assets (streams, previews, images)
• Supporting external or custom playback implementations
• Logging playback activity outside of the API Suite

Unlike the API Suite, the Catalogue Feed:

• Does not rely on user context
• Is typically used in server-to-server or batch workflows
• Prioritises data portability and control over real-time interaction

3. Interoperability

The API Suite and Catalogue Feed are fully interoperable and can be used independently or together.

Common integration patterns include:

• API Suite only​ For building complete streaming or media applications with user accounts, playback, and personalisation
• Catalogue Feed only​ For ingesting and managing a local catalogue or powering external playback systems
• Hybrid approach
  • Catalogue data is synchronised via the Catalogue Feed
  • User experiences, playback control, and personalisation are handled via the API Suite

This separation allows developers to choose the right model based on performance, architecture, and product requirements.

4. API Endpoints and Swagger

The platform is exposed through three primary API surfaces:

• API Suite:
  • Metadata API (Swagger)​ – A component of the API Suite, it provides catalogue and content access
  • Services API (Swagger)​ – A component of the API Suite, it provides user, playback, and transactional operations
• Catalogue Feed API (Swagger)​ – Manages catalogue metadata feed, asset access, reporting and external playback support

Each API has its own base URL, authentication model, and endpoint definitions. Information here.

5. Choosing the Right Approach

6. Documentation Structure

This documentation reflects the combined structure of the platform:

• Core API Suite domains (Search, Artists, Albums, Tracks, Stations, Playlists, Users, Billing, etc.)
• Unified presentation of Metadata and Services capabilities within each domain
• A dedicated section for ​Catalogue Feed (CDS)​, covering ingestion, asset delivery, and logging

Refer to the navigation for a full breakdown of endpoints and capabilities.