X post replies, newest first
The newest replies to a post, as TikHub returns it. A different shape from `/twitter/comments` despite the neighbouring name: this one answers with a `timeline` list and no parent post, ordered newest first. Returns third-party personal data in bulk — see `/legal/privacy`.
/v1/twitter/comments-latestThe newest replies to a post, as TikHub returns it.
A different shape from /twitter/comments despite the neighbouring name: this one
answers with a timeline list and no parent post, ordered newest first.
Returns third-party personal data in bulk — see /legal/privacy.
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/comments-latest?tweet_id=string"{ "cache_age": 0, "cached": false, "credits_remaining": 0, "credits_used": 0, "data": {}, "schema_version": "2", "success": true, "took_ms": 0}X following GET
One page of the accounts a user follows, as TikHub returns it. Returns third-party personal data in bulk — see `/legal/privacy`. Unlike `/twitter/followers`, an unknown handle answers 400 upstream rather than an empty page.
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.