Docs

Every `/v1/*` endpoint needs a TikData key. Keys look like `thr_live_` followed by 48 hex characters, and each one belongs to exactly one project — that is how spend gets attributed without any client-side tracking code.

Every error is JSON with an `error` string and, where it helps, a `hint`:

One post from any of the four platforms, normalized to a single shape. Pass the post's URL; the platform is detected from it.

The batch form of [`/v1/post`](/docs/post.md). Up to 500 URLs per request, platforms mixed freely, fanned out server-side at the router's own concurrency and rate limit. One slow or dead post never blocks the rest.

Up to 100 videos per call, platforms mixed freely, identified by id or URL, flattened to one row per video with every engagement stat the platform exposes. One entry out per entry in, in order, each with its own `ok`, so a single dead id never fails the batch.

The creator behind the posts — one shape across TikTok, Instagram, YouTube and X. Pass a profile URL, or a bare handle with `platform`.

Followers now, plus everything a creator published in the last N days and how it performed. One request whatever the paging underneath — the walk follows each platform's cursor until a page reaches past the window, the feed runs out, or a six-page cap stops it.

Verbatim pass-through to the upstream provider. Anything TikData has no custom endpoint for is reachable here, so adopting the router never blocks you on us adding something first. The caller's key selects the project for attribution; the real upstream key never leaves the server.

Which key and project am I calling as. The health check to run when wiring up a new consumer — it costs nothing upstream.

Per-key calls and cost for a day. A consumer key sees its own usage; the admin token sees every key. Cost is computed **live** at query time, never stored.

The upstream account meter, read live. **Admin only** — a consumer key has no business seeing account-wide spend.

Admin only. Send the deployment's `INGEST_TOKEN` as `x-admin-token`. The plaintext key is returned **exactly once**, at creation; only its SHA-256 hash is stored.