InsightSocial
GET /v1/twitter/tweet/replies

Twitter/X Tweet Replies API

Returns the replies to a tweet, each with the reply text, author info, like and reply counts, and creation time. The tweet itself is not in the list.

10 credits a call · cursor pagination · failed calls free · 10 free calls to start

curl "https://api.insightsocial.app/v1/twitter/tweet/replies?url=https%3A%2F%2Fx.com%2FNews24%2Fstatus%2F2093257170653483101" \
-H "x-api-key: $INSIGHTSOCIAL_API_KEY"
200 OKJSON
{
"success": true,
"platform": "twitter",
"endpoint": "/v1/twitter/tweet/replies",
"schema_version": "2",
"data": {
"items": [
{
"comment": {
"id": "<string>",
"url": "<string | null>",
"parent_id": "<string | null>",
"post_id": "<string | null>",
"text": "<string | null>",
"author": {
"id": "<string | null>",
"username": "<string | null>",
"display_name": "<string | null>",
"avatar_url": "<string | null>",
"verified": "<boolean | null>"
},
"engagement": {
"likes": "<integer | null>",
"replies": "<integer | null>"
},
"flags": {
"pinned": "<boolean | null>",
"deleted": "<boolean>"
},
"published_at": "<string | null>",
"language": "<string | null>",
"replies": "<array | null>",
"ext": "<object | null>"
}
}
]
},
"pagination": {
"next_cursor": "<string | null>",
"has_more": "<boolean>"
},
"unavailable": [],
"credits_used": "<integer>"
}

When to use it

Use it with a tweet URL to read the conversation under it; the cursor walks deeper threads, and a tweet with no replies returns an empty list.

Parameters

Query parameters for GET /v1/twitter/tweet/replies. Send your key in the x-api-key header.

NameRequiredDescription
urlYesFull URL of the tweet to fetch replies for
cursorNoCursor from the previous response's pagination.next_cursor to fetch more replies. It remembers sort and since_id, so you do not need to send them again
sortNoReply order: latest for the newest replies first, with later pages continuing in time order, or relevance for the platform's ranking. Leave it out for the default ranking, which is not in time order
since_idNoThe newest reply id from your last check (digits only). Returns only replies newer than it, newest first, and stops once it reaches older ones, so no next_cursor comes back after that; it also reads the next page once, so a reply X served a page late is not missed. A check with nothing new returns an empty list and costs nothing. Sets sort=latest; sort=relevance with it is a free 400
sinceNoOnly rows published on or after this date: YYYY-MM-DD (midnight UTC) or an ISO 8601 timestamp. Rows older than it are left off the page, and the page that reaches one ends the walk: next_cursor is not returned and pagination.stopped_at is since. Sending it sets the newest-first sort shown in this endpoint's sort parameter (any other sort value is a free 400). The page still costs what a page costs, so you pay for the pages you walk and no more. A row with no date is kept.
untilNoOnly rows published on or before this date: YYYY-MM-DD (that whole UTC day is included) or an ISO 8601 timestamp. Newer rows are left off each page and the walk does not stop, so older pages follow. A row with no date is kept.
max_pagesNo1 to 50 (default 1). Walk up to this many pages in one call and return the rows from all of them.
max_age_sNoThe oldest cached copy you accept, in seconds. A copy that old or younger is served, with its age in age_s and the X-Cache-Age header. Without it a copy up to 300 seconds old is served. A lower value fetches fresh (billed) when the copy is older, and 0 always fetches live, like Cache-Control: no-cache.

Response fields

The same unified schema every typed endpoint returns, so code written for Twitter/X reads the other platforms too. A field the platform did not provide is null and listed in unavailable.

FieldTypeNotes
idstringAn identifier, always a string. Never parse it as a number: several platforms use ids above 2^53.
urlstring | null
parent_idstring | nullAn identifier, always a string. Never parse it as a number: several platforms use ids above 2^53.
post_idstring | nullAn identifier, always a string. Never parse it as a number: several platforms use ids above 2^53.
textstring | null
author.idstring | null
author.usernamestring | null
author.display_namestring | null
author.avatar_urlstring | null
author.verifiedboolean | null
engagement.likesinteger | nullA count. null when the platform does not expose it; 0 only when it is really zero.
engagement.repliesinteger | nullA count. null when the platform does not expose it; 0 only when it is really zero.
flags.pinnedboolean | null
flags.deletedboolean
published_atstring | nullISO-8601 timestamp in UTC, ending in Z.
languagestring | nullThe content's language as the platform states it, e.g. en, pt-BR. Detected languages come later (§7.1).
repliesarray | null
extobject | nullPlatform-specific fields, snake_case.

Every field, error and example is in the Twitter/X Tweet Replies API reference.

How much does the Twitter/X Tweet Replies API cost?

10 credits per successful call.

  • Failed calls are free

    A call that errors or finds nothing costs 0 credits.

  • Know the price first

    Add dry_run=1 and the response quotes the call without making it. Nothing is charged.

  • One balance

    API calls and Chrome extension exports share the same credits, on the free plan too.

Twitter/X Tweet Replies API: frequently asked questions

Send GET /v1/twitter/tweet/replies with the url parameter and your key in the x-api-key header. Returns the replies to a tweet, each with the reply text, author info, like and reply counts, and creation time. The tweet itself is not in the list.