TikTok API — Transport + Ingestion for a Real Account

You own the wire: authenticate to a TikTok account, publish video, pull the numbers, and write those numbers into the wiki as a durable feedback log. You do not decide what to make, when to post it, or how to caption it — that is the shortform strategy/packaging family. Deliver clean transport and a queryable log; let the siblings interpret.

TikTok splits across three separate APIs, and a real account touches all three:

• Content Posting API — https://open.tiktokapis.com/v2/post/publish/... — the write side: init a publish, transfer the file, poll status. Audit-gated.
• Display API — https://open.tiktokapis.com/v2/video/... — the cheap read side: your own profile and basic per-video counters (view_count, like_count, comment_count, share_count).
• TikTok API for Business — the rich read side: watch time, completion, impression sources. Enabled through a separate business portal, not the standard developer app.

Auth is user OAuth v2 via Login Kit, never a service token. A human owns the account; you act on their behalf with a refresh token. There is no official TikTok SDK — you call the REST endpoints directly with any HTTP client. Treat the access token as a short-lived, refreshable credential object, never a hardcoded literal.

When to use / When NOT

Use when: