Platforms & distributors

The Platforms registry (Settings → Platforms, platform-admin only) defines what each distribution destination is — YouTube, TikTok, a podcast feed, a stock marketplace — and how JARAI talks to it. This is the platform-wide definition, distinct from an operator connecting their own account to a channel.

Registry vs connection

This page defines the platform (its encoding rules, API endpoints, quotas). An operator separately authorises their account’s channel via OAuth on Connected platforms. One is the platform definition; the other is one account’s link to it.

🎬 Configure a distribution platform

Prefer to read? Open the step-by-step transcript

1. Open Settings → Platforms and pick a platform.
2. Review its identity & status — name, asset type, adapter, active flag.
3. Check the encoding specs, API connectivity and quota/health settings.
4. Save changes — they apply platform-wide to every account that publishes there.

What a platform record holds

Group	Examples
Identity & status	Name, adapter key (immutable code identifier), whether the adapter is implemented, active flag, asset type, distribution method
Encoding specs	Max duration & file size, default + supported aspect ratios, video/audio codecs, frame rate, caption burn-in / sidecar format
Connectivity & auth	Publish/upload/status endpoints, API version headers, auth scheme, token endpoint, whether PKCE is required
Quota & health	Rate-limit window + limit, max publications/day, outage threshold, poll interval, async-upload flag
Market intelligence	Monthly active users, last-verified date, docs URL, an assessment note
Health (read-only)	Current health status, last successful publication, last failure + code, quota used/reset

The adapter-pairing rule

Every platform is backed by a code adapter identified by its adapter key. The adapter key field itself is immutable once set — the API rejects any attempt to change it. Whether active and adapter implemented agree is not checked by the system, though: they’re independent fields, so it’s on the admin to keep them honest. Set a platform active before its adapter ships and the first publish attempt fails with “adapter not found” rather than being blocked up front — so treat “don’t activate before the adapter is live” as a discipline the Console won’t enforce for you, not a guardrail it will.

Caution

The adapter key is immutable, and the pairing matters at publish time: an active platform with a missing or mismatched adapter produces “adapter not found” failures on the first publish attempt — not at save time.

Platforms vs distributors

• A platform is a single destination (YouTube, TikTok, a podcast directory) with its own encoding and API rules.
• A distributor is a third party that delivers to several platforms on JARAI’s behalf. A platform record can be linked to an existing distributor when that partner manages it, but only through the Admin API (PATCH on the platform’s distributorId) — the Settings → Platforms page has no distributor field. Creating or editing a distributor itself isn’t available from the Console either — distributor records are reference data set up behind the scenes, not something an admin configures here.

Where it shows up

What you configure here drives how the Distribution loop encodes and publishes, and feeds the Distribution and Alert operations dashboards and provider-health views in Operations & reliability.