Docs
One HTTP API over the platforms we cover. Every call is a POST to a named path with a JSON body, authenticated by one key, priced by the shape of the request rather than the platform answering it. TikTok is what is live today; 18 endpoints, each with a page of its own.
Every call
There is no pass-through route and no query-string API. If a path is not in the reference, it is not served — which means the surface you are building against is the surface we test, price, and keep working.
A 200 hands you the platform's own body, unchanged. We do not rename fields, drop them, or wrap them in an envelope of ours. That is the whole bargain: you get what you came for, and you decode it yourself.
POST https://api.sorina.sh/v1/{platform}/{endpoint}
authorization: Bearer sor_live_…
content-type: application/json
{ "field": "value" }Start here
A key, one call, and the next page of results.
The key, the header, and what a refusal means.
What a call takes, what comes back, and the two things that catch people.
Offsets, cursors, and the search id that pages a search.
Every code, what it means, and which are worth retrying.
What a call costs, when it is charged, and what stops you.
The endpoints
Grouped by what they cost. A class describes the request, not the platform behind it, which is why the price list survives adding one. Each page carries the body fields, an example in four languages, and an honest account of what comes back — including where we have not seen enough to say.
All paths are relative to https://api.sorina.sh/v1/tiktok. The full table, with each body, is on the endpoint index.