GET /api/v1/x/trends

Trends

Changed on Oct 20, 2026

Returns X's current trends for a place you choose. Pick it by woeid, country or location name. Without one, trends are worldwide. Add at to read what was trending on Twitter at a past time, such as yesterday. Xquik keeps a Twitter trends archive from 2026-10-13 02:20 UTC on, with 1 list per place every 5 minutes. Each request costs 1 credit, however many trends it returns.

get/api/v1/x/trends

Request

Base URL: https://xquik.com
URL: https://xquik.com/api/v1/x/trends
Auth: one of:
- API key in header x-api-key
- HTTP bearer
- none

Query parameters

woeidinteger

Region WOEID (1=Worldwide, 23424977=US, 23424975=UK, 23424969=Turkey). Wins over country & location.

countrystring

Country to read trends for, by name or 2-letter code, such as Turkey or TR. Case insensitive. X can add places, so Xquik takes up to 280 characters, the most a post holds.

locationstring

Town or country to read trends for, by name, such as Istanbul. Case insensitive. Add country when 2 towns share a name. /x/trends/locations lists every name. X can add places, so Xquik takes up to 280 characters, the most a post holds.

countinteger

Number of trending topics to return (1-50, default 30)

atstring

A past time, to read what was trending on Twitter then. Takes an ISO 8601 time, a date such as 2026-10-13, or Unix seconds. A time without a zone reads as UTC. It also takes a span back from now, as a number & s, m, h or d. So at=24h reads what was trending on Twitter yesterday at this hour, on every run of a schedule. The answer is the stored list nearest that time, with its own time in capturedAt. History starts 2026-10-13 02:20 UTC. A time over 24 hours from every stored list answers 400 at no charge.

fieldsstring

Example:id,text,author.username

Fields to keep in each row, comma-separated. Use dots for nested fields, such as author.username. A list keeps the field in each item. Case & underscores do not matter. A row that lacks a field leaves it out. Cursors, counts & diagnostics always stay. An unknown name answers 400 unknown_field with the valid names, before any read. The price stays the same. SDK row types then hold only the named fields. A longer URL fails at the edge before Xquik reads it.

omitstring

Example:entities,media

Fields to drop from each row, comma-separated. It takes the same names as fields. With fields, it drops from the kept fields. A longer URL fails at the edge before Xquik reads it.

Response

List of trending topics

countinteger required

woeidinteger required

capturedAtstring date-time

When Xquik read this list from X. It comes from the stored list and is never estimated.

requestedAtstring date-time

The time the at parameter asked for, as Xquik read it. A span such as 24h shows here as the time it counted back to. Present only with at.

Example response

{
  "trends": [
    {
      "name": "#AI",
      "description": "Artificial intelligence discussions",
      "promotedContent": null,
      "query": "%23AI",
      "rank": 1,
      "tweetVolume": 250000,
      "url": "https://x.com/search?q=%23AI"
    }
  ],
  "count": 30,
  "woeid": 1,
  "location": {
    "woeid": 2344116,
    "name": "Istanbul",
    "country": "Turkey",
    "countryCode": "TR",
    "placeType": "Town",
    "placeTypeCode": 7,
    "parentWoeid": 23424969,
    "url": "http://where.yahooapis.com/v1/place/2344116"
  },
  "capturedAt": "2026-10-13T14:00:26.000Z",
  "requestedAt": "2026-10-13T14:00:00.000Z"
}

Changes

Oct 20, 202645942c75fdc2 Revision changes
- warning
  added the new topup_in_progress enum value to the ///// response property for the response status
- warning
  added the new topup_in_progress enum value to the ////// response property for the response status
- warning
  added the new topup_in_progress enum value to the / response property for the response status
- warning
  added the new topup_in_progress enum value to the / response property for the response status
- warning
  added the new topup_in_progress enum value to the / response property for the response status
- warning
  added the new topup_in_progress enum value to the / response property for the response status
- warning
  added the new topup_in_progress enum value to the / response property for the response status
- warning
  added the new topup_in_progress enum value to the / response property for the response status
- warning
  added the new topup_in_progress enum value to the / response property for the response status
- warning
  added the new topup_in_progress enum value to the // response property for the response status
- warning
  added the new topup_in_progress enum value to the // response property for the response status
- warning
  added the new topup_in_progress enum value to the // response property for the response status
- warning
  added the new topup_in_progress enum value to the // response property for the response status
- warning
  added the new topup_in_progress enum value to the // response property for the response status
- warning
  added the new topup_in_progress enum value to the // response property for the response status
- warning
  added the new topup_in_progress enum value to the // response property for the response status
- warning
  added the new topup_in_progress enum value to the ////// response property for the response status
- warning
  added the new topup_in_progress enum value to the /////// response property for the response status

Operation history