Intro to Platform API

Platform API is how platforms, distributors, labels, and developers join the Wav Linq network. Integrate the Detection and Embed APIs into your pipelines, and your platform becomes a node — scanning audio as it moves, recovering embedded Linq IDs, and resolving attribution at scale. While Creator Hub is where creators embed and track their work, Platform API is what makes universal detection real: the same signal-level extraction that works in the app, wired into upload flows, catalog matching, and content moderation across the open web.

If Creator Hub is where creators establish proof, Platform API is how that proof reaches them wherever their audio ends up — node by node, automatically, at platform scale.

What is the Platform API?

Wav Linq splits into two sides. Creator Hub gives creators a place to embed Linq IDs, run manual extraction, and watch attributions accumulate. Platform API exposes that same watermarking engine through APIs so partners don't need to rebuild signal analysis themselves.

Each integration is a node in the network. A distributor scanning uploads, a social app checking clips, a label watermarking a catalog — each one extends detection reach for every creator on Creator Hub.

Platform API has two primary surfaces:

Detection API — submit audio, recover embedded Linq IDs, resolve attribution metadata
Embed API — watermark catalogs at scale with federated resolution, so your metadata stays in your database

Both use the same DB-backed API key system. See the Partner API docs and API status to get started.

Detection API

The Detection API runs asynchronous watermark extraction. A platform uploads audio, receives a job_id immediately, and polls until the job succeeds or fails. Typical jobs complete in a few seconds.

POST /api/detect/jobs          → submit audio, get job_id (202)
GET  /api/detect/jobs/<id>     → poll until status is succeeded or failed

This design fits production integration: rate-limited, auth-gated, and idempotency-keyed so retries don't spawn duplicate work. When a Linq ID is found, the node resolves it against the Wav Linq registry or, for federated partners, against your HTTPS resolver endpoint.

That's universal detection in practice. Every integrated platform becomes a detection node. Creators in Creator Hub don't upload files to each service individually; nodes find their Linq IDs as audio passes through partner pipelines and attribute the work back to them.

What platforms get back

A successful detection returns the embedded Linq ID, an attribution_source indicating how metadata was resolved, and track/creator fields when available — title, artist, ISRC, rights holder, and more. Platforms can use this for credit display, rights workflows, catalog deduplication, or feeding attribution events back to creators via Creator Hub.

Federated resolution

For partners who keep catalog metadata in their own systems, the Platform API stores only a routing pointer, not your full track records. When detection finds a Linq ID registered to your account, your node calls your resolver URL and returns the metadata you supply.

Your database can be anything. Wav Linq never connects to it directly; it GETs your HTTPS endpoint. PostgreSQL, DynamoDB, a bespoke catalog service — the resolver contract is the integration surface.

Embed API

The Embed API watermarks audio and registers a resolver URL in one step — built for distributors, labels, and platforms embedding at catalog scale.

POST /api/v1/partner/embed    → watermarked WAV + signature headers

Pass audio_file and a resolver URL (resolver_endpoint or resolver_base_url + optional resolver_path_template). Your node returns a watermarked attachment with the embedded Linq ID in response headers (X-WavLinq-Signature, X-WavLinq-Partner-Account-ID).

Federated embed means Wav Linq handles signal encoding; you handle metadata ownership. When anyone later runs detection through the Platform API or through Creator Hub's extract page, resolution calls your endpoint. Your catalog data never has to live in our registry.

How Platform API powers Creator Hub

Creators in Creator Hub embed Linq IDs and check suspect files through the web app. Platform API extends that same detection to every integrated node:

A creator embeds in Creator Hub
Their audio spreads across distributors, social apps, and streaming services
Nodes scan audio through the Detection API
Matches resolve to the creator's Linq ID
Attributions surface in the creator's Attributions feed and Creator Hub dashboard

Creator Hub is the creator experience. Platform API is the detection fabric underneath — a network of nodes, each one extending reach for every creator. Without it, attribution depends on creators manually uploading copies. With nodes integrated across platforms, credit follows the audio.

Who is Platform API for?

Platforms and social apps that want to become a detection node on upload or in catalog matching.

Labels and distributors watermarking releases at scale via the Embed API.

Developers building rights, credit, or content-integrity workflows on top of signal-level identity.

If you're integrating Wav Linq into a product rather than using the creator app directly, Platform API is your entry point.

Getting started

Sign up or log in to a developer account
Create API keys on the API keys page
Read the Partner API docs for request shapes, auth headers, and resolver implementation
Check API status before going to production