# X Tweet Replies API (https://www.socialcrawl.dev/platforms/twitter/tweet-replies)

> Returns the replies to a specific tweet, each with the reply text, author info, like count, reply count, and creation timestamp. The tweet itself is not included in the list, and a tweet with no replies returns an empty list. Page size is set by the source. Deeper threads are a cursor walk: send `pagination.next_cursor` back as `cursor` and repeat until `pagination.has_more` is false; each page costs 1 credit. Without `sort`, replies come in the platform's own ranking, not in time order. `sort=latest` returns replies newest first, and the cursor remembers the sort, so later pages continue in time order (X occasionally serves one reply a page late, at the top of the next page). To check for new replies, send `since_id` set to the newest reply id from your last check: the call returns only newer replies, newest first, and stops once it reaches older ones, so a check with nothing new returns an empty list and costs nothing. When the main source cannot fetch the first page, a second source answers with up to 40 direct replies and no cursor, so that response is the whole list; it cannot keep replies in time order, so a `sort=latest` or `since_id` call is answered by the main source only.

TL;DR: `GET /v1/twitter/tweet/replies` costs 1 credit per page, with the default labels (sentiment, question, purchase_intent, complaint) included free. label=spam, toxic or low_quality holds 4 extra credits and refunds down to 1 credit per started 25 comments that were newly judged: comments already labelled are free, a page where nothing could be judged refunds the whole extra, and a cached page is free. With `max_pages`, `max_items` or `max_credits`, each page walked is billed at this price (a cached page is free), and `max_credits` caps the total. and returns SocialCrawl's unified JSON schema. Single x-api-key auth, 100 free credits on signup.

## Parameters

| Parameter | Required | Description |
| --- | --- | --- |
| `url` | yes | Full URL of the tweet to fetch replies for |
| `cursor` | no | Cursor 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 |
| `sort` | no | Reply 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 (relevance \| latest) |
| `since_id` | no | The 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 |
| `label` | no | Optional CSV of SocialCrawl labels to add to every comment: sentiment, spam, question, purchase_intent, complaint, toxic, low_quality, injection. Without this param every page already carries sentiment, question, purchase_intent and complaint, free; label= adds the labels you name to them (the defaults keep running). Each comment gains computed.labels with probabilities (0 to 1), so you choose the cut-off; a comment that could not be judged carries labels: null. sentiment, question, purchase_intent and complaint are free when asked for too; spam, toxic, low_quality and injection add 1 credit per started 25 newly judged comments (comments already labelled for anyone are free, and so is a cached page). injection flags text that addresses an AI system and tries to direct it (flagged, p); it never drops or rewrites a row. judgments=off (or label=none) turns the default labels off. data.labels reports what was judged and billed. |
| `exclude` | no | Optional CSV (spam, low_quality), only with the same preset in label. Drops comments whose probability is 0.8 or higher and lists their ids in data.labels.dropped_ids. A comment that could not be judged is never dropped. |
| `judgments` | no | Optional, on (the default) or off. By default every row gains free SocialCrawl judgments (computed.labels, and computed.relevance on search endpoints), reported in data.labels (mode default) and data.relevance (origin default), each with a status (complete, partial or skipped) and pending: the rows still being judged when the page was sent, which carry null now and are filled on your next call or cached read. Default judgments never add credits, never change an existing field, and never drop or reorder a row. off returns the page exactly as before, with none of those keys. label=none does the same. (on \| off) |
| `dry_run` | no | Optional. When 1, return a cost preview for this labelled or relevance-filtered request without fetching the page or judging any row. data.estimate reports rows_expected, rows_cached, label_credits_min, label_credits_max and base_credits. 0 credits charged. (1) |
| `label_evidence` | no | Optional, only with label=. When 1, every labelled row also carries computed.labels_evidence.<preset> = { quote, sentence_index }: the sentence in the row that most clearly shows the label, copied verbatim. Absent or null when no single sentence shows it. (1) |
| `fit` | no | Optional. When goal, keep the rows and fields needed for the goal you pass in goal= (plus any that are uncertain, and the first and last), and replace the rest with a stub. data.held_back lists the held ids and a recall id that re-reads the full page from cache at no extra charge. Without this param the page is unchanged. (goal) |
| `goal` | no | Required by fit=goal. What you are trying to do, in your own words, up to 300 characters. |
| `fit_tokens` | no | Optional, only with fit=goal. Soft cap on how much of the page to keep, in tokens. Uncertain blocks and the first and last block are kept even if they exceed it. |
| `since` | no | Only 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. `published_after`, `start_date`, `from_date`, `publish_time` (`yesterday`, `this-week`, `this-month`, `last-3-months`, `last-6-months`) and `max_age_days` are accepted and applied as `since`. |
| `until` | no | Only 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. `published_before`, `end_date` and `to_date` are accepted and applied as `until`. |
| `max_pages` | no | 1 to 50 (default 1, or 50 when `max_items` or `max_credits` is sent). Walk up to this many pages in one call and return the rows from all of them. Each page walked is billed exactly as one call to this endpoint (a cached page is free) and counts against your rate limit; its charge and any refund are recorded under the page's own request id, listed in `data.walk.request_ids`. The walk stops early at the last page, or when the request's time budget runs low; `data.walk.stopped` says why (`end`, `max_pages`, `max_items`, `max_credits`, `time_budget`, `page_error`) and `pagination.next_cursor` continues from where it stopped. |
| `max_items` | no | 1 to 5000. Get more in one call: keep walking pages until the response holds at least this many rows, then stop with `data.walk.stopped: "max_items"`. The last page is returned whole (it was billed), so `data.items` can hold up to one page more than this, and `pagination.next_cursor` resumes right after it without skipping a row. Walks up to 50 pages unless `max_pages` says fewer; each page is billed as one call (a cached page is free). Add `max_credits` to cap the spend. A long walk can stop on the time budget first (`"time_budget"`): send the returned cursor with the same params to continue. |
| `max_credits` | no | 1 to 100000. The most this call may spend, across every page it walks. A page starts only while the credits already spent plus that page's price (or, when higher, the most any page of this walk has cost) still fit, so the call never goes past it; the walk then stops with `data.walk.stopped: "max_credits"` and the cursor to resume. Sent alone, it walks as far as the budget goes (up to 50 pages). A value below the price of one page is a free 400 whose `error.details.page_credits` names that price. Credits a row join (`include=`) adds are known only once a page has run, so page 1 is checked against its own price. |

## Code example

```bash
curl -G "https://www.socialcrawl.dev/v1/twitter/tweet/replies" \
  --data-urlencode "url=https://x.com/News24/status/2093257170653483101" \
  -H "x-api-key: sc_YOUR_API_KEY"
```

## FAQ

### What does the X Tweet Replies API return?

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. The response uses the same JSON envelope as every SocialCrawl endpoint, with the data, credits_used and request_id fields.

### When should I use the X Tweet Replies endpoint?

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.

### How much does the X Tweet Replies API cost?

The price depends on the request, from 1 to 5 credits per call. Every new account gets 100 free credits. Credits for failed or empty calls are refunded automatically, and there is no subscription.

### What parameters does the X Tweet Replies API need?

The one required parameter is url (full URL of the tweet to fetch replies for). It also accepts 16 optional parameters, all listed on this page. The optional parameter to try first is label (Marks each comment that shows buying intent, at no extra credits; sentiment, question and complaint are free too).

### How do I call the X Tweet Replies API?

Send a GET request to https://www.socialcrawl.dev/v1/twitter/tweet/replies?url=https%3A%2F%2Fx.com%2FNews24%2Fstatus%2F2093257170653483101 with your API key in the x-api-key header. An Authorization: Bearer header works too.

See the full X API: https://www.socialcrawl.dev/platforms/twitter

## Pricing

- Standard endpoints: 1 credit per call
- Advanced endpoints: 5 credits per call
- Premium endpoints: 10 credits per call
- 100 free credits on signup, no credit card required. Cached responses cost 0 credits. Credit packs never expire.
- Full pricing: https://www.socialcrawl.dev/pricing

## Explore with AI

Questions this API answers, phrased for an AI assistant:

- What does the SocialCrawl X Tweet Replies API return?
- How do I get X Tweet Replies data with the SocialCrawl API?