Tweets

Tweet with replies

A tweet with its author, media, counts and the reply thread.

Paginated: pass the bottom cursor of one page as cursor to get the next. Each page is one billed call.

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

get/tweet/{tweetId}

Request

  • Base URL: https://api.twittrapi.com
  • URL: https://api.twittrapi.com/tweet/{tweetId}
  • 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

rankingMode'Relevance' | 'Recency' | 'Likes'

Order of the replies, passed to X: Relevance, Recency or Likes.

includePromotedContentboolean

Ask X to include promoted tweets. Accepts true/false, 1/0.

cursorstring

Cursor from the previous page to load more replies.

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 of X's TweetDetail query. The focal tweet and replies are entries in data.threaded_conversation_with_injections_v2.instructions. X sends about 20 to 35 reply threads (conversationthread entries) per page; the page size is fixed. The bottom cursor is an entry with cursorType "Bottom" at the end of the entries.

With format=simple: Collection of Tweet objects: {data: [Tweet], nextCursor, previousCursor, hasNextPage}. The conversation in display order: ancestors, the tweet itself, then replies; threads (modules) are flattened.

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.