Tweet thread: GET /tweet/{tweetId}/thread

Docs

Tweet thread

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

GET/tweet/{tweetId}/thread

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

Parameters

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

Name	In	Type	Required	Description
tweetId	path	string	yes	Numeric tweet ID (digits only, up to 30), the number at the end of the tweet URL.

Example request

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

import httpx

# No SDK method for this endpoint yet, so this is a plain HTTP call.
resp = httpx.get(
    "https://api.twittrapi.com/tweet/20/thread",
    headers={"X-API-KEY": "YOUR_API_KEY"},
    timeout=60,
)
data = resp.json()

import { TwittrAPI } from "twittrapi";

const client = new TwittrAPI({ apiKey: process.env.TWITTRAPI_API_KEY });
// No wrapper method for this endpoint yet; client.get() sends the same authenticated GET.
const data = await client.get({
  path: "/tweet/20/thread",
});

curl 'https://twitter-aio.p.rapidapi.com/tweet/20/thread' \
  --header 'x-rapidapi-key: YOUR_RAPIDAPI_KEY' \
  --header 'x-rapidapi-host: twitter-aio.p.rapidapi.com'

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 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.

Simple format (?format=simple or X-Response-Format: simple): Collection of Tweet objects: {data: [Tweet], nextCursor, previousCursor, hasNextPage}. The thread in reading order, on one page. 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.