Tweets

Tweet thread

The author's own thread around a tweet: their tweets above it and their replies to themselves below it.

The thread ends at the first reply by someone else. Long threads are loaded in the same request; it is still one billed call.

Reference: https://www.twittrapi.com/docs/reference/tweet-tweetid-thread

get/tweet/{tweetId}/thread

Request

  • Base URL: https://api.twittrapi.com
  • URL: https://api.twittrapi.com/tweet/{tweetId}/thread
  • Auth: API key in header X-API-KEY

Path parameters

tweetIdstring required

Numeric tweet ID (digits only, up to 30), the number at the end of the tweet URL.

Query parameters

format'raw' | 'simple'

raw (default): X's JSON passed through. simple: flat camelCase JSON with a fixed schema and a {data, nextCursor, previousCursor, hasNextPage} envelope. Same price. The header X-Response-Format: simple does the same.

Response

Raw JSON in the shape of X's TweetDetail query with one TimelineAddEntries instruction: the thread in reading order as tweet entries. When the tweet itself is not available (deleted or withheld), X's answer is returned unchanged.

With format=simple: Collection of Tweet objects: {data: [Tweet], nextCursor, previousCursor, hasNextPage}. The thread in reading order, on one page.

OR
RawPassthrough required

X's own JSON (raw format, the default), passed through unchanged. The shape is X's and can change; see https://www.twittrapi.com/docs/response-format.

Changes

No recorded changes to this operation across all 1 revision of this API.