X user timeline
One page of an X/Twitter user's posts, as TikHub returns it. Each item carries `favorites`, `retweets`, `replies`, `quotes`, `bookmarks` and `views`, plus `conversation_id` and `retweeted_tweet` — which is how replies and retweets are told apart from original posts. Page size is the vendor's to choose; there is no `count`. To page, pass the previous response's `next_cursor` as `cursor`.
/v1/twitter/tweetsOne page of an X/Twitter user's posts, as TikHub returns it.
Each item carries favorites, retweets, replies, quotes, bookmarks and
views, plus conversation_id and retweeted_tweet — which is how replies and
retweets are told apart from original posts.
Page size is the vendor's to choose; there is no count. To page, pass the previous
response's next_cursor as cursor.
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/tweets?username=string"{ "cache_age": 0, "cached": false, "credits_remaining": 0, "credits_used": 0, "data": {}, "schema_version": "2", "success": true, "took_ms": 0}X user replies GET
One page of a user's replies to other people, as TikHub returns it. The timeline routes exclude replies, so this is the other half of an account's output rather than a filter over the same data.
Your past calls GET
Your own call history, newest first. Free — it reads our table, not the vendor. **`request` and `response` are null unless the deployment enables the call log** (`CALL_LOG_DAYS`, ADR-036), which is off by default. The rest of each row — endpoint, credits, cached, timestamp — has always been recorded and is what billing runs on. Bodies are opt-in per request rather than always included. A page of fifty payloads is megabytes, and a caller listing "what did I call yesterday" wants neither the bytes nor the wait; `include=response` is for the caller who is replaying one. Scoped to `ctx.key.user_id` in the query itself rather than filtered afterwards. That is the difference between a bug that leaks another customer's history and a query that cannot express it.