Skip to main content
GET
/
x
/
trends
Get X trends
curl --request GET \
  --url https://xquik.com/api/v1/x/trends \
  --header 'x-api-key: <api-key>'

Documentation Index

Fetch the complete documentation index at: https://docs.xquik.com/llms.txt

Use this file to discover all available pages before exploring further.

3 credits per call · All plans from $0.00012/credit
curl -G https://xquik.com/api/v1/x/trends \
  --data-urlencode "woeid=23424977" \
  --data-urlencode "count=10" \
  -H "x-api-key: xq_YOUR_KEY_HERE" | jq
Use GET /x/trends when a workflow needs ranked regional topics for content planning, monitor seeding, search jobs, or alert routing. The examples write one JSON line per trend. Store trend_name, rank, description, search_query, region_woeid, and returned_count, then pass search_query to Search Tweets when a job needs matching tweets.

​
Query parameters

​
woeid
integer
Positive Where On Earth ID for the region. Invalid or nonpositive values fall back to 1 (worldwide). See Trends guide for common regions.
​
count
integer
Number of trends to return. Default 30, max 50. Invalid or below-minimum values fall back to 30.

​
Headers

​
x-api-key
string
required
Your API key. Session cookie authentication is also supported.

​
Response

​
trends
object[]
Array of trending topics.
​
count
number
Number of trends returned.
​
woeid
number
WOEID used for the request.
{
  "trends": [
    {
      "name": "#AI",
      "rank": 1,
      "description": "Trending in Technology",
      "query": "%23AI"
    }
  ],
  "count": 1,
  "woeid": 23424977
}
This endpoint returns trends directly from X. For multi-source trending data (Google Trends, Hacker News, Reddit, etc.), use List Radar Items.
Next steps: Search Tweets to find tweets about a trending topic.
Last modified on May 17, 2026