X / Twitter API

X / Twitter Search API

Search X (Twitter) with full advanced-search syntax (operators like from:, since:, until:, min_faves: work inline in the query) and get structured tweets with text, author, engagement, and cursor pagination. Limit is a per-page maximum; native pages contain approximately 20 tweets unless requireSinglePage selects a bulk lane.

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

What the API returneditems[0]
{
"id":ย "1928912345678901234",
"url":ย "https://x.com/duskdevlog/status/1928912345678901234",
"text":ย "gpt-6 handling multi-file refactors without losing context is the first time an LLM diff actually felt safe to auto-apply",
"authorUsername":ย "duskdevlog",
"authorName":ย "Dusk Ibrahim",
"authorVerified":ย true,
"authorId":ย "1758912340000000000",
"authorImage":ย "https://pbs.twimg.com/profile_images/1758912340000000000/dusk_avatar.jpg",
... 13 more fields
}
Uptime
99.99%
30d ยท 2,091,402 calls
Requests
2.1M
30d ยท weekly, last 12 wks
Response
1.4s
median ยท 30d

Try it

Get X / Twitter search 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. A named field can still be absent on a post that genuinely lacks it. 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.

This sample shows 29 of 31 fields. See every field

{
  "found": true,
  "data": {
    "items": [
      {
        "id": "1928912345678901234",
        "url": "https://x.com/duskdevlog/status/1928912345678901234",
        "text": "gpt-6 handling multi-file refactors without losing context is the first time an LLM diff actually felt safe to auto-apply",
        "authorUsername": "duskdevlog",
        "authorName": "Dusk Ibrahim",
        "authorVerified": true,
        "authorId": "1758912340000000000",
        "authorImage": "https://pbs.twimg.com/profile_images/1758912340000000000/dusk_avatar.jpg",
        "authorFollowers": 18400,
        "likeCount": 2840,
        "retweetCount": 312,
        "replyCount": 88,
        "quoteCount": 14,
        "viewCount": 412000,
        "bookmarkCount": 640,
        "createdUtc": 1758240000,
        "lang": "en",
        "isReply": false,
        "conversationId": "1928912345678901234",
        "inReplyToId": null,
        "media": []
      },
      {
        "id": "1928912345678901235",
        "url": "https://x.com/laurenshipsit/status/1928912345678901235",
        "text": "openai just quietly bumped the context window again, nobody noticed because everyone is busy arguing about pricing",
        "authorUsername": "laurenshipsit",
        "authorName": "Lauren Ostrowski",
        "authorVerified": false,
        "authorId": "1601234567890123456",
        "authorImage": "https://pbs.twimg.com/profile_images/1601234567890123456/lauren_avatar.jpg",
        "authorFollowers": 6200,
        "likeCount": 960,
        "retweetCount": 140,
        "replyCount": 52,
        "quoteCount": 6,
        "viewCount": 98400,
        "bookmarkCount": 210,
        "createdUtc": 1758153600,
        "lang": "en",
        "isReply": false,
        "conversationId": "1928912345678901235",
        "inReplyToId": null,
        "media": [
          {
            "type": "photo",
            "url": "https://pbs.twimg.com/media/GZsearchScreenshot.jpg",
            "width": 1080,
            "height": 1350
          }
        ]
      },
      {
        "id": "1928912345678901236",
        "url": "https://x.com/samthebuilder/status/1928912345678901236",
        "text": "replying to the thread below, openai's function calling still trips on nested optional fields half the time",
        "authorUsername": "samthebuilder",
        "authorName": "Sam Whitfield",
        "authorVerified": false,
        "authorId": "1489012345678901234",
        "authorImage": "https://pbs.twimg.com/profile_images/1489012345678901234/sam_avatar.jpg",
        "authorFollowers": 940,
        "likeCount": 88,
        "retweetCount": 3,
        "replyCount": 12,
        "quoteCount": 0,
        "viewCount": 5400,
        "bookmarkCount": 9,
        "createdUtc": 1758067200,
        "lang": "en",
        "isReply": true,
        "conversationId": "1928912345678901230",
        "inReplyToId": "1928912345678901229",
        "media": []
      }
    ],
    "nextCursor": "DAACCgACGZabc123DEF456"
  }
}

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-31 ยท uptime and latency measured over 30d

Request body

JSON, posted to this endpoint.

  • querystring

    openai gpt-6

    Search query using X (Twitter) advanced-search syntax. IMPORTANT: bare terms are ANDed - a tweet must contain EVERY word, so a list of loosely related keywords matches nothing; use one short phrase or OR between alternatives (e.g. 'anyapi OR getanyapi'). When an operator follows an OR list, put the list in parentheses, e.g. '(anyapi OR getanyapi) -filter:replies': without them X applies the operator to the last alternative only, so such a query still runs as X reads it and the response's hint carries the corrected query. You can embed X advanced-search operators directly in the query to filter results: from:username and to:username (author or recipient), since:YYYY-MM-DD and until:YYYY-MM-DD (date range), min_faves:N, min_retweets:N, min_replies:N (engagement floors), "exact phrase", -term to exclude, filter:media and filter:links and -filter:replies (content filters), lang:en, near:city, and geocode:lat,long,radius. Examples: 'from:OpenAI', 'AI agents min_faves:500 -filter:replies', 'nvidia since:2026-01-01 until:2026-03-01'. A query with no matches returns an empty items array; prefer the fewest words that identify the topic.

  • cursorstring

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

  • limitinteger

    Page size to ask for (1-50, default 20). Some sources honor it; others always return their whole native page of about 20. A page is never trimmed after the call, so follow nextCursor to continue exactly where this response ended.

  • queryTypeenum

    Latest

    Which posts to return: 'Latest' (newest first, the default), 'Top' (most popular), 'Photos' (newest posts with images), or 'Videos' (newest posts with video). Photos and Videos search your query as written with filter:images or filter:videos added after it, so they cost the same as a Latest search.

  • 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. A named field can still be absent on a post that genuinely lacks it. 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.

  • requireSinglePageboolean

    Set true to get up to limit results in one response instead of provider-native pages, served by a bulk provider when needed.

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

Response

JSON, one example value per field.

each itemdata.items[]

Tweet records: text, author profile, timestamp, and engagement metrics (likes, retweets, replies, views). Populated whenever the provider has data for the entity.

  • authorFollowersinteger

    18400

    Follower count of the account that posted.

  • authorIdstring

    1758912340000000000

    Numeric X user id of the account that posted, as a string.

  • authorImagestring

    https://pbs.twimg.com/profile_images/1758912340000000000/dusk_avatar.jpg

    Avatar image URL of the account that posted.

  • authorNamestring

    Dusk Ibrahim

    Populated whenever the provider has data for the entity.

  • authorUsernamestring

    duskdevlog

    Populated whenever the provider has data for the entity.

  • authorVerifiedboolean

    true

  • bookmarkCountinteger

    640

  • conversationIdstring

    1928912345678901234

  • createdUtcnumber

    1758240000

    UTC epoch timestamp in seconds (Unix time). Multiply by 1000 for a JS Date in milliseconds. Populated whenever the provider has data for the entity.

  • idstring

    1928912345678901234

    Populated whenever the provider has data for the entity.

  • inReplyToIdstring

    null

    Id of the post this post directly replies to, as a string, or null when the post is not a reply.

  • isReplyboolean

    false

  • langstring

    en

  • likeCountinteger

    2840

  • quoteCountinteger

    14

  • replyCountinteger

    88

  • retweetCountinteger

    312

  • textstring

    gpt-6 handling multi-file refactors without losing context is the first time an LLM diff actually felt safe to auto-apply

    Populated whenever the provider has data for the entity.

  • urlstring

    https://x.com/duskdevlog/status/1928912345678901234

    Populated whenever the provider has data for the entity.

  • viewCountinteger

    412000

    Number of views. Null when the source does not report it, as for posts older than X view counts.

each mediadata.items[].media[]

Photo, video, and GIF attachments on the post. Empty when the post has none.

  • heightinteger

    Pixel height of the media item, when the lane reports it.

  • typestring

    One of photo, video, or gif.

  • urlstring

    Image URL. For a video or GIF this is the poster/thumbnail frame. X media URLs on pbs.twimg.com are publicly fetchable without authentication; append ?name=orig for the full-resolution original.

  • videoUrlstring

    Playable video file URL. Present only for video and gif items.

  • widthinteger

    Pixel width of the media item, when the lane reports it.

datadata
  • nextCursorstringcan require

    DAACCgACGZabc123DEF456

    Opaque cursor for the next page of search results, or null when there are no more. Pass it back as cursor to continue.

top level
  • foundboolean

    true

  • reason"not_found"

    Present only when `found` is false, and says why there is no result. `not_found`: the source states the target does not exist, or returned nothing for it. A `found: false` answer is a successful call, not an error, and `costUsd` is what it actually cost.

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

Selling this API? See the full schema your endpoint must return.

FAQ

About the X / Twitter Search API

The AnyAPI X / Twitter Search API returns X / Twitter search data as normalized JSON from one POST call to /v1/run/twitter.search. Search X (Twitter) with full advanced-search syntax (operators like from:, since:, until:, min_faves: work inline in the query) and get structured tweets with text, author, engagement, and cursor pagination. Limit is a per-page maximum; native pages contain approximately 20 tweets unless requireSinglePage selects a bulk lane. AnyAPI routes each request across 4 sources and falls back automatically when one fails. It costs from $0.54 per 1,000 requests, in US dollars with no subscription and no monthly minimum. Over the last 30 days, 100.0% of X / Twitter search calls through AnyAPI succeeded, with a median response time of 1.4 seconds across 2,091,402 measured calls.

It costs from $0.54 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.

Search X (Twitter) with full advanced-search syntax (operators like from:, since:, until:, min_faves: work inline in the query) and get structured tweets with text, author, engagement, and cursor pagination. Limit is a per-page maximum; native pages contain approximately 20 tweets unless requireSinglePage selects a bulk lane. 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 search calls through AnyAPI succeeded, with a median response time of 1.4 seconds across 2,091,402 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 185 X / Twitter Search calls at $0.00054 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.search 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.