Docs
Tweet replies

Tweet replies

Only the replies to a tweet, without the tweet itself or the tweets above it.

GET/tweet/{tweetId}/replies

Parameters

  • tweetIdpath · string · required

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

  • rankingModequery · string · optional · default Relevance

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

  • includePromotedContentquery · boolean · optional · default false

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

  • cursorquery · string · optional

    Cursor from the previous page to load more replies.

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

Example request

curl 'https://api.twittrapi.com/tweet/20/replies' \
  --header 'X-API-KEY: YOUR_API_KEY'

Base URL https://api.twittrapi.com, key in the X-API-KEY header. Python and Node.js use the official SDKs.

Response

Raw JSON in the shape of X's TweetDetail query, like /tweet/{tweetId}, with only the reply threads (conversationthread entries) and the cursors for more replies. The tweet itself, the tweets above it and X's suggestions are removed.

Simple format (?format=simple or X-Response-Format: simple): Collection of Tweet objects: {data: [Tweet], nextCursor, previousCursor, hasNextPage}. The replies in display order; threads (modules) are flattened. Schema.

Example response coming soon.

In the raw format, field names and nesting come from X and can change without notice. See Response format; the simple format keeps a fixed schema.

Errors

  • 422tweetId is not numeric.
  • 404X reports the tweet as not found.

Errors every endpoint can return (401, 402, 403, 404, 408, 409, 429, 5xx), and which of them are charged, are on the Errors page. Calls that fail with 400, 407, 408, 409 or a 5xx error are refunded.