X post
One X/Twitter post by id, as TikHub returns it. The id is the long number at the end of a post URL. **Old ids are not served**: the 2006 post `20` answers 400, while a 2022-era id answers 200 with the full object. Where the cutoff sits has not been measured, so treat a 400 here as "too old or not public" rather than as a malformed id.
/v1/twitter/tweetOne X/Twitter post by id, as TikHub returns it.
The id is the long number at the end of a post URL. Old ids are not served: the
2006 post 20 answers 400, while a 2022-era id answers 200 with the full object.
Where the cutoff sits has not been measured, so treat a 400 here as "too old or not
public" rather than as a malformed id.
Query Parameters
Max acceptable age of a cached result, in seconds. A lower value demands fresher data; it does not shorten what is stored.
Response Body
application/json
application/json
curl -X GET "https://example.com/v1/twitter/tweet?tweet_id=string"{ "cache_age": 0, "cached": false, "credits_remaining": 0, "credits_used": 0, "data": {}, "schema_version": "2", "success": true, "took_ms": 0}X post replies GET
A post and its reply thread, as TikHub returns it. **Not a bare list.** Despite the vendor calling this "comments", the payload is the post itself — `id`, `text`, `author`, counters — with the replies under `thread`. That is why this route's content key is `id`: the post is what proves the call answered. Returns third-party personal data in bulk — see `/legal/privacy`. Replies carry their authors' handles, display names and avatar URLs verbatim, and nothing is hashed.
X profile GET
One X/Twitter user profile, as TikHub returns it. Carries `created_at`, `friends` and `sub_count` — account age and the following/follower ratio, which is what an authenticity signal is built from. A handle that does not exist answers `502 extraction_empty` and is not charged: the upstream returns `{"status": "notfound"}` with every other field null, which is why this route's content key is `rest_id` rather than "anything at all".