Fingerprinting Quick Start

Overview

Tuned Global supports audio fingerprinting use cases by providing secure, controlled access to catalogue media for bulk audio analysis. This allows fingerprinting and audio recognition (ACR) providers to process tracks within Tuned Global's infrastructure without media files leaving the platform boundary — a requirement of most licensing arrangements.

Fingerprinting is not a standalone Tuned Global API. Instead, Tuned Global facilitates fingerprinting by offering two integration models depending on how the client's analysis pipeline is architected.

Integration Models

Model 1 — On-Platform Analysis (Hosted Environment)

Tuned Global provisions dedicated virtual machines within its infrastructure. Clients install their own fingerprinting software on these VMs and process media directly, with access to tracks via an internal HTTP endpoint.

How it works:

1. Tuned Global provisions a Linux VM (Debian or Ubuntu) within the platform environment
2. Client receives SSH access over a public IP
3. Media is accessed via an internal HTTP endpoint — client requests tracks by ID and format
4. The client's fingerprinting software runs on the VM and processes audio locally
5. Fingerprint data is sent back to the client's own servers

Key characteristics:

• Media never leaves Tuned Global's infrastructure boundary
• No OAuth or token-based authentication required — access is controlled via source IP whitelist and partner ID
• Content access is restricted by a label group whitelist on a per-partner basis
• Suitable for bulk analysis workloads

VM Specifications:

Both standard disk and SSD variants are available. Contact Tuned Global to select the right specification for your workload.

Media access endpoint:

GET /track/{trackId}/format/{formatId}?partnerId={partnerId}

Authentication:

Requests are authenticated by the combination of source IP and partner ID — no OAuth signing is required. Tuned Global configures an IP whitelist during setup.

Recommended formats:

The endpoint returns the exact format requested. If the requested format is unavailable for a track, it returns HTTP 404 rather than a lower-bitrate substitute. Implement a fallback strategy: request AAC 256 first, then retry with FLAC if unavailable, or vice versa depending on your analysis requirements.

Model 2 — Remote Catalogue Access (API-Driven)

For clients who run fingerprinting infrastructure externally, Tuned Global provides remote API access to catalogue metadata and search. The client uses the standard Metadata API to discover and identify tracks, then performs fingerprinting analysis on their own systems.

How it works:

1. Client authenticates via OAuth2 (POST https://api-authentication-connect.tunedglobal.com/oauth2/token)
2. Client uses the Metadata API to search, browse, or retrieve catalogue data
3. Track metadata (IDs, ISRCs, artist/album data) is used to drive the fingerprinting pipeline on the client's own infrastructure
4. Fingerprint results are stored and managed on the client's systems

Relevant Metadata API endpoints:

All Metadata API requests require the StoreId header. See the Swagger API Explorer for full endpoint documentation.

Example — search for a track by ISRC:

curl -X GET "https://api-metadata-connect.tunedglobal.com/api/v2.4/search/search-matching?isrc=USUM71507297" \
  -H "StoreId: YOUR_STORE_ID"

Example — retrieve full track metadata:

curl -X GET "https://api-metadata-connect.tunedglobal.com/api/v2.4/songs/12345" \
  -H "StoreId: YOUR_STORE_ID"

Which model to use

Getting Started

For on-platform analysis (Model 1):

1. Contact Tuned Global to request a fingerprinting VM
2. Select a VM specification (Standard, Premium, or Platinum; standard disk or SSD)
3. Provide the source IP addresses to be whitelisted
4. Receive SSH credentials and partner ID
5. Install your fingerprinting software on the VM
6. Access media via the internal HTTP endpoint using track IDs from catalogue feeds
7. Implement AAC 256 / FLAC format fallback for track availability

For remote catalogue access (Model 2):

1. Obtain a StoreId and OAuth2 credentials from Tuned Global
2. Authenticate via POST https://api-authentication-connect.tunedglobal.com/oauth2/token
3. Use catalogue search and metadata endpoints to discover and retrieve track data
4. Feed track identifiers (IDs, ISRCs) into your fingerprinting pipeline
5. Store and manage fingerprint results on your own infrastructure

Swagger References

• Metadata API (v2.4) — Catalogue search, track metadata, ISRC matching
• Services API (v3) — Authentication, user context, playback services