Trend locations
All places X has trends for, with their WOEIDs.
/misc/locationsParameters
None.
Example request
curl 'https://api.twittrapi.com/misc/locations' \
--header 'X-API-KEY: YOUR_API_KEY'from twittrapi import TwittrAPI
client = TwittrAPI(api_key="YOUR_API_KEY")
data = client.trends.locations()import { TwittrAPI } from "twittrapi";
const client = new TwittrAPI({ apiKey: process.env.TWITTRAPI_API_KEY });
const data = await client.trends.locations();curl 'https://twitter-aio.p.rapidapi.com/misc/locations' \
--header 'x-rapidapi-key: YOUR_RAPIDAPI_KEY' \
--header 'x-rapidapi-host: twitter-aio.p.rapidapi.com'Base URL https://api.twittrapi.com, key in the X-API-KEY header. Python and Node.js use the official SDKs.
Response
Raw JSON of X's v1.1 trends/available endpoint: an array of places with name, woeid, country and placeType.
Simple format (?format=simple or X-Response-Format: simple): Collection of TrendLocation objects {woeid, name, country, countryCode, placeType, parentId} (no cursor). Schema.
In the raw format, field names and nesting come from X and can change without notice. See Response format; the simple format keeps a fixed schema.
Errors
No endpoint-specific validation. Errors from X are mapped as described below.
Errors every endpoint can return (401, 402, 403, 404, 408, 409, 429, 5xx), and which of them are charged, are on the Errors page. Calls that fail with 400, 408, 409 or a 5xx error are refunded.