Trends API

X Trends

X trending topics by WOEID, cached in MySQL and exposed through private SOUND.RADAR endpoints.

Overview

What this API is for

This API collects public X trend pages from trends24.in, stores snapshots in MySQL, and serves cached results by location slug or WOEID-compatible IDs.

Access

Public path and credentials

Basehttps://api.soundradar.co/x-trends

AuthProtected data endpoints require X-API-Key.

UpstreamUses public trends24.in pages instead of the paid official X Trends API.

Endpoints

Available routes

GET/x-trends/health

Public service health and latest configured location snapshots.

GET/x-trends/locations

Supported location slugs and WOEIDs. Requires X-API-Key.

GET/x-trends/trends/{location_slug}

Latest cached trends by slug, e.g. worldwide, south-korea, seoul, tokyo.

GET/x-trends/trends/by-woeid/{woeid}

Latest cached trends by numeric WOEID.

POST/x-trends/refresh

Manually fetch and cache one location from the configured public trend source.

Examples

Requests

curl -H "X-API-Key: $SOUND_RADAR_API_KEY" \
  "https://api.soundradar.co/x-trends/trends/worldwide?limit=20"

curl -H "X-API-Key: $SOUND_RADAR_API_KEY" \
  "https://api.soundradar.co/x-trends/trends/by-woeid/1118370?limit=20"

Operations

Runtime notes

The service runs from /opt/soundradar-collectors/x-trends on internal port 8060. The refresh timer is active and stores public trend snapshots in the xtrend MySQL database.