# X / Twitter Post Replies (`twitter.replies`)

Replies to a public X (Twitter) post as structured records with author, text and engagement, cursor-paged about 20 per page.

Docs: https://primaryapi.com/docs/api-reference/twitter/replies

- Endpoint: `POST https://api.primaryapi.com/v1/run/twitter.replies`
- Category: Social · Platform: `twitter` · Kind: list · Status: live
- Price: 2 credits per call; up to 4 credits if a call is retried elsewhere. A quote’s `maxCredits` is the most a given call can cost.
- Billing unit: per successful call
- Reliability: routed to a healthy upstream and retried automatically when an attempt fails; live 30-day status: `GET https://api.primaryapi.com/v1/status/apis?sku=twitter.replies`
- Execution: synchronous (answers 202 only if it outlives the wait window)

## Input

| Field | Type | Required | Default | Constraints | Description |
|---|---|---|---|---|---|
| `url` | string | yes |  | max 2048 chars; pattern: ^\s*(?:\d{1,25}\|(?:https?:\/\/)?(?:[a-z0-9-]+\.)*(?:x\|twitter)\.com\/[^\s]*?\/status(?:es)?\/\d{1,25}(?:[/?#][^\s]*)?)\s*$ | Full URL of the X (Twitter) post to fetch replies for (e.g. https://x.com/nasa/status/1846987139428634858), or its numeric id. |
| `limit` | integer | no | 40 | 1–40 | Maximum number of results to return (1-40, default 40). |
| `cursor` | string | no |  |  | Opaque pagination cursor: pass the previous response's nextCursor. |

Unknown fields are rejected with `400 invalid_input`. The routing controls `preferLatencyUnderMs` and `maxCredits` may be sent in the same JSON body.

## Output

When `output.found` is `true`, `output.data` has this shape:

| Field | Type | Description |
|---|---|---|
| `items` | object[] |  |
| `items[].id` | string | Reply post id |
| `items[].url` | string |  |
| `items[].text` | string \| null |  |
| `items[].createdUtc` | integer \| null | UTC epoch seconds |
| `items[].lang` | string \| null |  |
| `items[].authorHandle` | string \| null |  |
| `items[].authorId` | string \| null |  |
| `items[].authorName` | string \| null |  |
| `items[].conversationId` | string \| null |  |
| `items[].inReplyToId` | string \| null |  |
| `items[].likeCount` | integer \| null |  |
| `items[].replyCount` | integer \| null |  |
| `items[].quoteCount` | integer \| null |  |
| `items[].repostCount` | integer \| null |  |
| `items[].viewCount` | integer \| null |  |
| `items[].media` | object[] |  |
| `items[].media[].type` | string \| null | photo \| video \| animated_gif |
| `items[].media[].url` | string \| null | Image URL (the poster frame for videos) |
| `items[].media[].videoUrl` | string \| null | Direct video URL for video and GIF media |
| `items[].media[].width` | integer \| null |  |
| `items[].media[].height` | integer \| null |  |
| `nextCursor` | string \| null | Pass back as `cursor` for the next page; null at the end |

When the thing you asked about does not exist (or a search matches nothing) the call still succeeds: `output.found` is `false`, `output.data` is `null` and `output.reason` says why (`not_found`, `private`, `no_results`, …). Misses are free unless the notes below say misses are billed.

Pagination: pass the previous response’s `nextCursor` as `cursor` to get the next page; `nextCursor: null` means there are no more results.

## Example request

```bash
curl -sS -X POST "https://api.primaryapi.com/v1/run/twitter.replies" \
  -H "Authorization: Bearer $PRIMARYAPI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://x.com/NASA/status/1846987139428634858"}'
```

## Example response

_Values are placeholders that follow the output schema; `credits` is what this call would cost at the usual price._

```json
{
  "output": {
    "found": true,
    "data": {
      "items": [
        {
          "id": "string",
          "url": "https://x.com/NASA/status/1846987139428634858",
          "text": "string",
          "createdUtc": 0,
          "lang": "string",
          "authorHandle": "string",
          "authorId": "string",
          "authorName": "string",
          "conversationId": "string",
          "inReplyToId": "string",
          "likeCount": 0,
          "replyCount": 0,
          "quoteCount": 0,
          "repostCount": 0,
          "viewCount": 0,
          "media": [
            {
              "type": "string",
              "url": "https://x.com/NASA/status/1846987139428634858",
              "videoUrl": "https://example.com",
              "width": 0,
              "height": 0
            }
          ]
        }
      ],
      "nextCursor": null
    }
  },
  "provider": "PrimaryAPI",
  "credits": 2,
  "items": 1,
  "requestId": "req_01JBXK6Y2N9V8T4R3Q2P1M0A7Z",
  "nextCursor": null
}
```

## Pricing and reliability

- Usual price: 2 credits per call
- Price ceiling: up to 4 credits if a call is retried elsewhere. A quote’s `maxCredits` is the most a given call can cost; the `maxCredits` routing control caps it per call
- Live 30-day status, success rate, uptime and latency: `GET https://api.primaryapi.com/v1/status/apis?sku=twitter.replies`

## Errors to handle

`invalid_input`, `unauthorized`, `insufficient_balance`, `key_limit_reached`, `trial_cap_reached`, `forbidden`, `not_found`, `idempotency_conflict`, `rate_limited`, `all_sources_failed`, `service_unavailable`, `timeout`. See https://primaryapi.com/docs/errors.

## Notes

Sources return their native page (~20). An empty page is found=false (no_results) and does not assert whether the post exists.

