X trends API

X trends data in one REST call — normalized to the stable JSON schema shared across every FetchPI platform.

1 documented endpoints
GET /v1/x/trends

Contract summary (English): Get trends (capability x.trends)

Normalized response entity: x/trends
capability: x.trends

Every response also carries freshness (cache / default / live) and billing metadata.

Use cases

Find {{platform}} content and accounts matching a keyword, with normalized results ready for scoring.
Follow trending topics and hot lists to catch emerging conversations early.
Alert on search and trend queries so your team sees shifts as they happen.

Response fields

X trends (normalized non-entity payload)

Field	Type	Required	Description
platform	"x"	Required	—
type	"trends"	Required	—
country	string \| null	Optional	The requested country (the ?q value); null when omitted.
trends	object[]	Required	—
fetched_at	string	Required	—

Field notes are shown in the contract's original English.

Response meta

Field	Type	Required	Description
mode	cache \| default \| live	Required	Effective mode after merging param > max_age > source policy (D-004).
age_seconds	integer \| null	Optional	Age of served data; null when unknown.
source_layer	cache \| db \| upstream	Required	Which layer served the response (PRD §10).
stale	boolean	Optional	True when stale data was served under stale_if_error / SWR (D-004).
billing.amount_credits	integer	Required	Micro-USD (1e-6 USD) actually charged for this request.
billing.cache_hit	boolean	Required	—

Field notes are shown in the contract's original English.

Example request & response

GET/v1/x/trends

curl -H "Authorization: Bearer $MESHDATA_API_KEY" \
  "https://api.fetchpi.com/v1/x/trends?q=meshdata"

{
  "data": {
    "platform": "x",
    "type": "trends",
    "country": "united states",
    "trends": [
      {
        "name": "#MeshData",
        "post_count": 52341
      },
      {
        "name": "Normalized Entities",
        "post_count": 8800,
        "url": "https://x.com/search?q=normalized"
      }
    ],
    "fetched_at": "2026-09-18T09:00:00Z"
  },
  "meta": {
    "request_id": "req_01HTXQ8Z9HTQ",
    "freshness": {
      "mode": "default",
      "age_seconds": 0,
      "source_layer": "upstream",
      "stale": false
    },
    "billing": {
      "amount_credits": 100,
      "cache_hit": false
    }
  }
}

Free demo

Create a free account, grab an API key and call this endpoint from the browser-based Playground.

Try it in the Playground

Parameter tables, error codes and response semantics for this endpoint live in the API documentation.

Open the endpoint reference

Frequently asked questions

What is the difference between cache and live freshness?

cache answers from the stored snapshot without touching the upstream; live queries fresher data and may cost extra credits — see the freshness section of the docs.

Can I try this endpoint for free?

Yes — register an account, grab an API key and call it from the Playground in the console.

How is the trends capability billed?

Data API calls are billed per request in credits, with different cache/live freshness multipliers. Current per-capability prices live on the pricing page.

Pricing

Per-request credit billing with cache/live freshness options — current prices live on the pricing page.

View pricing Browse all APIs