X / Twitter API

X / Twitter Replies API

Fetch the replies to any X (Twitter) post URL as structured records: author, text, and engagement. An empty result is valid and does not assert whether the target post exists.

$0.45/1k req, pay per request, no subscription.

Post
x.com/nasa/status/1846987139428634858

Post

N

nasa

@nasa

M

Mars Watcher@marswatcher · Oct 21, 2024

This never gets old. Godspeed to the next crew.

412340
What the API returneditems[0]
{
"id": "1846991234567890111",
"url": "https://x.com/marswatcher/status/1846991234567890111",
"text": "This never gets old. Godspeed to the next crew.",
"authorName": "Mars Watcher",
"authorHandle": "marswatcher",
"replyCount": 4,
"repostCount": 12,
"likeCount": 340,
+4 more fields
}
Uptime
99.98%
30d · 8,391 calls
Requests
8,392
30d · weekly, last 12 wks
Response
1.7s
median · 30d

Try it

Get X / Twitter replies in one request

requireFieldsarray
Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `nextCursor`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. Naming a combination that no single source returns together is refused as invalid input, with no charge. On a paginated walk it applies to the first page only; later pages stay with the source that page chose, at the price it was quoted.
Open in
Get a free key
Sample response
Free runs return only the first 3 results. Fund a key to get the full response.
{
  "found": true,
  "data": {
    "items": [
      {
        "id": "1846991234567890111",
        "url": "https://x.com/marswatcher/status/1846991234567890111",
        "text": "This never gets old. Godspeed to the next crew.",
        "authorName": "Mars Watcher",
        "authorHandle": "marswatcher",
        "replyCount": 4,
        "repostCount": 12,
        "likeCount": 340,
        "quoteCount": 1,
        "viewCount": 18400,
        "createdUtc": 1729526400,
        "media": []
      },
      {
        "id": "1846991234567890112",
        "url": "https://x.com/rocketrhea/status/1846991234567890112",
        "text": "Watched the launch live from the causeway, the ground shakes more than you would think",
        "authorName": "Rhea Ibarra",
        "authorHandle": "rocketrhea",
        "replyCount": 2,
        "repostCount": 5,
        "likeCount": 96,
        "quoteCount": 0,
        "viewCount": 5200,
        "createdUtc": 1729526460,
        "media": [
          {
            "type": "photo",
            "url": "https://pbs.twimg.com/media/GZreplyLaunchpad.jpg",
            "width": 1200,
            "height": 800
          }
        ]
      },
      {
        "id": "1846991234567890113",
        "url": "https://x.com/coldcoffeeorbit/status/1846991234567890113",
        "text": "",
        "authorName": "Cold Coffee Orbit",
        "authorHandle": "coldcoffeeorbit",
        "replyCount": 0,
        "repostCount": 1,
        "likeCount": 22,
        "quoteCount": 0,
        "viewCount": 1100,
        "createdUtc": 1729526520,
        "media": [
          {
            "type": "video",
            "url": "https://pbs.twimg.com/amplify_video_thumb/1846991234567890113/img/reply_video_poster.jpg",
            "videoUrl": "https://video.twimg.com/amplify_video/1846991234567890113/vid/720x1280/reply_video.mp4",
            "width": 640,
            "height": 360
          }
        ]
      }
    ],
    "conversationId": "1846987139428634858"
  }
}

Full parameter and response reference - every field, type, and example for this endpoint.

Reference

One request, one response shape.

Every field you send and every field you get back, each with a real example.

Last verified 2026-10-06 · uptime and latency measured over 30d

Request body

JSON, posted to this endpoint.

  • urlstring

    https://x.com/nasa/status/1846987139428634858

    Full URL of the X (Twitter) post to fetch replies for (e.g. https://x.com/nasa/status/1846987139428634858).

  • cursorstring

    Opaque pagination cursor from a previous response's nextCursor. Omit for the first page; pass it to fetch the next page of replies.

  • limitinteger

    Maximum number of results to return (1-40, default 40). Per-result lanes cost less at lower limits; a backup that bills its native page may cost up to the advertised request price.

  • requireFieldsarray

    Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `nextCursor`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. Naming a combination that no single source returns together is refused as invalid input, with no charge. On a paginated walk it applies to the first page only; later pages stay with the source that page chose, at the price it was quoted.

You send. A small JSON body. The values shown are examples to replace with your own.

Response

JSON, one example value per field.

  • foundboolean

    true

each itemdata.items[]
  • idstring

    1846991234567890111

  • urlstring

    https://x.com/marswatcher/status/1846991234567890111

  • textstring

    This never gets old. Godspeed to the next crew.

  • authorNamestring

    Mars Watcher

  • authorHandlestring

    marswatcher

  • replyCountnumber

    4

  • repostCountnumber

    12

  • likeCountnumber

    340

  • quoteCountnumber

    1

  • viewCountnumber

    18400

  • createdUtcnumber

    1729526400

  • mediaarray
datadata
  • conversationIdstring

    1846987139428634858

You get back. Named, typed fields in the same shape whichever source answers.

FAQ

About the X / Twitter Replies API

The AnyAPI X / Twitter Replies API returns X / Twitter replies data as normalized JSON from one POST call to /v1/run/twitter.replies. Fetch the replies to any X (Twitter) post URL as structured records: author, text, and engagement. An empty result is valid and does not assert whether the target post exists. AnyAPI routes each request across 4 sources and falls back automatically when one fails. It costs from $0.45 per 1,000 requests, in US dollars with no subscription and no monthly minimum. Over the last 30 days, 100.0% of X / Twitter replies calls through AnyAPI succeeded, with a median response time of 1.7 seconds across 8,391 measured calls.

It costs from $0.45 per 1,000 requests, in US dollars with no subscription and no monthly minimum. You fund one USD wallet and each call draws it down. Some failed wallet-funded requests incur processing charges that we pass through at cost, with no markup; the error response shows the amount charged.

Fetch the replies to any X (Twitter) post URL as structured records: author, text, and engagement. An empty result is valid and does not assert whether the target post exists. The response is normalized JSON with the same envelope every AnyAPI endpoint returns, so parsing a second endpoint is a change of URL and nothing else.

Over the last 30 days, 100.0% of X / Twitter replies calls through AnyAPI succeeded, with a median response time of 1.7 seconds across 8,391 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.

Yes. A new AnyAPI account starts with $0.10 of free balance and no card required, which covers 222 X / Twitter Replies calls at $0.00045 each.

AnyAPI asks the next of its 4 sources in the same request, cheapest first, so one source going down does not fail your call.

Send a POST request to https://api.getanyapi.com/v1/run/twitter.replies with your AnyAPI key in an "Authorization: Bearer" header and the input as a JSON body. The same key and the same wallet work on every AnyAPI endpoint.

No. You add US dollars to one prepaid AnyAPI balance and each request draws it down. There is no monthly plan and no minimum, and the same balance pays for every AnyAPI endpoint.

Yes. Install @getanyapi/sdk from npm for TypeScript or getanyapi from pip for Python. Both call every AnyAPI endpoint with the same key, and any HTTP client works too.

Yes. An agent can connect to the AnyAPI MCP server at https://api.getanyapi.com/mcp, or create its own free-trial key with one unauthenticated POST to https://api.getanyapi.com/agent/signup and call this endpoint over HTTP.