X / Twitter API

X / Twitter Trends API

Get current X (Twitter) trends for worldwide, a country, or a city in X ranking order, including the resolved location.

Start freeDownload sampleor JSON

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

Explore / X
x.com/explore/tabs/trending

Trending

United States

Trending in United States

#NBAOpeningNight

Trending in United States

Federal Reserve

Promoted

iPhone 18

Trending in United States

#MondayMotivation

Trending in United States

Coachella 2027

What the API returneditems[0]
{
"rank": 1,
"name": "#NBAOpeningNight",
"isHashtag": true,
"query": "%23NBAOpeningNight",
"promoted": false
}
Uptime
99.55%
30d · 670 calls
Requests
694
30d · weekly, last 12 wks
Response
1.6s
median · 30d

Pricing and providers

X / Twitter Trends API pricing: one API, 2 interchangeable providers

The cheapest provider serves first. If it fails, the next one takes over in the same call.

You pay
$1.00
$0.10/1k req, only for what you use. No monthly plan.
Your first 1,000 requests are free with the $0.10 starting balance.

Try it

Get X / Twitter trends 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 `promoted`, 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 trend that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge.
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": {
    "location": "United States",
    "locationId": "23424977",
    "asOfUtc": 1727366400,
    "items": [
      {
        "rank": 1,
        "name": "#NBAOpeningNight",
        "isHashtag": true,
        "query": "%23NBAOpeningNight",
        "promoted": false
      },
      {
        "rank": 2,
        "name": "Federal Reserve",
        "isHashtag": false,
        "query": "%22Federal%20Reserve%22",
        "promoted": false
      },
      {
        "rank": 3,
        "name": "iPhone 18",
        "isHashtag": false,
        "query": "%22iPhone%2018%22",
        "promoted": true
      },
      {
        "rank": 4,
        "name": "#MondayMotivation",
        "isHashtag": true,
        "query": "%23MondayMotivation",
        "promoted": false
      },
      {
        "rank": 5,
        "name": "Coachella 2027",
        "isHashtag": false,
        "query": "%22Coachella%202027%22",
        "promoted": false
      }
    ],
    "url": "https://x.com/search?q=%23NBAOpeningNight"
  }
}

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.

  • limitinteger

    10

    Maximum number of ranked trends to return (1-50, default 50).

  • locationstring

    United States

    Country name, city name, or ISO country code. Omit for worldwide trends.

  • 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 `promoted`, 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 trend that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge.

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

datadata
  • locationstring

    United States

  • locationIdstring

    23424977

  • asOfUtcnumber

    1727366400

  • urlstring

    https://x.com/search?q=%23NBAOpeningNight

each itemdata.items[]
  • ranknumber

    1

  • namestring

    #NBAOpeningNight

  • isHashtagbooleancan require

    true

  • querystring

    %23NBAOpeningNight

  • promotedbooleancan require

    false

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

FAQ

About the X / Twitter Trends API

The AnyAPI X / Twitter Trends API returns X / Twitter trends data as normalized JSON from one POST call to /v1/run/twitter.trends. Get current X (Twitter) trends for worldwide, a country, or a city in X ranking order, including the resolved location. AnyAPI routes each request across 2 sources and falls back automatically when one fails. It costs from $0.10 per 1,000 requests, in US dollars with no subscription and no monthly minimum. Over the last 30 days, 99.6% of X / Twitter trends calls through AnyAPI succeeded, with a median response time of 1.6 seconds across 670 measured calls.

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

Get current X (Twitter) trends for worldwide, a country, or a city in X ranking order, including the resolved location. 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, 99.6% of X / Twitter trends calls through AnyAPI succeeded, with a median response time of 1.6 seconds across 670 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 1,000 X / Twitter Trends calls at $0.0001 each.

AnyAPI asks the next of its 2 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.trends 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.
More to call

Other X / Twitter endpoints

Articlefrom $0.75 /1k reqCommunityfrom $0.10 /1k reqCommunity tweetsfrom $0.45 /1k reqFollowersfrom $0.45 /1k reqFollowingfrom $0.45 /1k reqProfilefrom $0.22 /1k reqRepliesfrom $0.45 /1k reqSearchfrom $0.60 /1k reqSearch communitiesfrom $0.11 /1k resultsSearch usersfrom $0.70 /1k reqThreadfrom $3.75 /1k reqTweetfrom $0.22 /1k reqTweet transcriptfrom $1.20 /1k reqUser postsfrom $0.45 /1k reqUser tweetsfrom $0.45 /1k req