Social Fetch
Get API key
X (Twitter) hub

X (Twitter) tweet replies API

Pass a public tweet permalink (or numeric id) and get reply posts with text, authors, and metrics — cursor-paged in the shared Social Fetch envelope.

GET /v1/twitter/tweets/replies

2 credits per successful request.

Try in playgroundFull API docs

About this endpoint

Moderation, brand listening, and research jobs often start from one status link and need the conversation under it. Single-tweet lookup gives you the parent post. Profile timelines give you what a handle published. Neither returns the reply thread hanging off a specific status.

`GET /v1/twitter/tweets/replies` takes a required `url` query param (an `x.com` / `twitter.com` `/status/...` permalink or a bare numeric tweet id) and an optional opaque `cursor`. On success, read `data.replies` and `data.page`. Each reply is a normalized tweet item: id, url, text, language, timestamps, conversation and parent ids when present, author card, engagement metrics, media, and reply/quote/retweet flags. Paginate by passing `data.page.nextCursor` as `cursor` while `hasMore` is true. The cursor is opaque; do not invent or parse it.

This route pages replies for one status. Parent post detail is `GET /v1/twitter/tweets`. A handle's timeline is `GET /v1/twitter/profiles/{handle}/tweets`. Spoken text from a video tweet is `GET /v1/twitter/tweets/transcript`. Pricing is on the credit badge for this operation; bill from `meta.creditsCharged` on every response.

X (Twitter) tweet replies API FAQ

How do I list replies to an X / Twitter tweet via API?

Call GET /v1/twitter/tweets/replies with your Social Fetch API key in the x-api-key header and a required url query param (tweet permalink or numeric id). Read data.replies and data.page. Full parameters and examples are in the API docs linked from this page.

How many credits does the Twitter tweet replies endpoint cost?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged — that field is the billing source of truth.

How does pagination work on tweet replies?

Each response includes data.page.nextCursor and data.page.hasMore. When hasMore is true, pass nextCursor as the cursor query param on the next request. The cursor is opaque — do not invent or parse it.

What fields are in each reply?

Each item can include id, public url, text, language, createdAt, conversationId, inReplyToStatusId, author (handle, displayName, avatarUrl, verification flags), metrics (likes, retweets, replies, quotes, views, bookmarks), media, and isReply / isQuote / isRetweet flags when present. Exact nullability lives in the OpenAPI schema for this route.

Tweet replies vs single tweet vs profile tweets?

Use this route for the reply thread under a status URL. Use GET /v1/twitter/tweets for one parent post by URL. Use GET /v1/twitter/profiles/{handle}/tweets to page a handle's timeline. They are separate marketplace operations with their own credit notes.

What URL formats does the tweet replies API accept?

Public tweet permalinks on x.com or twitter.com (/status/...) or a bare numeric tweet id. Pass one url per request. If the id cannot be parsed from url, the API returns a 400 validation error.

Do I need an X developer account for tweet replies?

No. Authenticate with your Social Fetch API key only. You do not create an X developer app or pass X Bearer tokens for this public replies list.

Other X (Twitter) endpoints