Twitter Trends API — Get Regional X Trend Labels
Use the Twitter Trends API to read regional trend labels by WOEID, with query links, location and observation timestamps. Keep unknown tweet volumes distinct from zero.
1 credit per successful request, including empty results. Failures are free.
https://api.goanyapi.com/api/v1/twitter/trending/labelsRun a request to see the visual result
The response is organized into metrics, lists and tables that match the JSON on the right.
Run a request to see the response here
Fill in the demo parameters to preview an example response for free. Sign in to send live requests with your own parameters.
Build a regional topic shortlist from a labelled observation
The Twitter Trends API helps editors inspect labels for a supported region, with query links and regional timestamps. Keep those fields together in a topic shortlist, then select entries for further reading. The API supplies the labels and observation context; an editor adds notes and chooses the subjects to pursue. It does not supply a complete regional trend history.
Saved example: the global label list
Use the optional woeid string "1" for the global selection; it is also the declared default. The saved result reports Worldwide and contains 50 labels, beginning with Steelers. Its asOf value is 2026-11-16T02:48:20Z and createdAt is 2026-11-15T06:55:37Z. Each entry has a name, query and URL; tweetVolume is null in the sample. Those timestamps describe the regional result, not when individual posts were published. A useful worksheet can retain the region, label, search link and unknown-volume marker together, followed by a separate column for your own editorial notes. See the regional trends documentation for the request and supported regions.
- data.result.location
- The saved location is Worldwide. Keep it beside the returned WOEID in the worksheet header so that every label remains attached to its regional observation.
- data.result.asOf
- Store this timestamp with createdAt as separate regional result metadata. Neither is a tweet publication date or a promised refresh interval; add your retrieval time separately.
- data.result.trends[].name
- Display the label, such as Steelers in the first saved entry. Preserve response order; any row number you add is a sequence number, not an absolute popularity rank.
- data.result.trends[].query
- Retain the original query alongside the displayed name and URL. These separate fields form a useful search reference; a trend name need not be a hashtag.
- data.result.trends[].tweetVolume
- Null means the volume is unknown, not zero. Preserve the raw value in your topic sheet rather than deriving posting activity or unique participant counts from missing information.
Use the supported region list and preserve uncertainty
WOEID is an optional string, defaults to the global value and accepts only the listed enumeration values. A topicId or placeId cannot substitute for it. This endpoint has no pagination and returns labels rather than tweet bodies. A saved 50-label response is an example, not a fixed result-size guarantee. Successful requests, including successful empty results, use the configured current fee; failures are free. Empty and missing business fields remain as returned.
Practical outputs from regional labels
Use returned labels to guide your own reading and record keeping. Follow-up research, comparisons and conclusions belong to the user’s workflow.
Prepare a region-labelled shortlist
An editor can place returned names and query links in a topic sheet headed by the selected region. The X regional trends API supplies the labels and observation context for choosing what to read next.
Keep the original search references
A research assistant can keep each entry’s URL, query and display name together. A reviewer then has the exact reference returned with the observation when deciding which topic deserves a separate reading task.
Preserve the received order
A dashboard can display every returned label in its received order and add row numbers for navigation. Keep those sequence numbers with the observation when exporting your own worksheet or organizing review notes.
Represent missing volume honestly
A reporting tool can show unknown for null tweetVolume and zero only for a returned zero. Keep the raw values beside the display labels so a reviewer can distinguish available figures from missing information.
Create your own observation log
A researcher can save regional timestamps alongside a client-recorded retrieval time. Later, place independently saved observations side by side to inspect changes in label presence and order for the same selected region.
Give an Agent a label-review task
An HTTP-capable Agent can request a supported WOEID and prepare a shortlist with original names, query links and unknown-volume markers. Configure authorization securely in the client and retain the regional timestamps in the brief.
Questions about scope, fields and requests
No. The input is a string selected from the supported WOEID list. The default string 1 selects the global context. Do not send an arbitrary number, a language selection, placeId or topicId as a substitute. Use the documented region choices for this endpoint.
No. This Twitter trends by WOEID API returns regional labels, query links and metadata. It does not return the associated post bodies or authors. The separate trend timeline endpoints concern posts and have different inputs; choosing one is another explicit request rather than a hidden expansion.
A null volume is unknown, not zero. List order is preserved, but a row number added by the interface is only a sequence number. Neither establishes an exact volume or absolute rank. Keep those distinctions visible if your own report groups or compares the labels.
The public contract supplies neither a historical date input nor pagination. Save observations in your own system if you need later comparisons, while recording their times. A new request obtains another result; it is not a continuation cursor or a guaranteed reconstruction of an earlier list.
Opening this page loads a saved example without querying. Each explicit successful request, including a successful empty result, uses the current configured rate; failed requests are free. Querying several regions requires separate requests. Check the displayed fee rather than assuming a fixed price or a bundled monitoring plan.
Continue from labels to a separate content question
Use the Twitter Trends API for regional labels. If you already know a post or account, inspect that resource separately; the trend tweet timeline offers a different reading context. Each follow-up request has its own inputs and configured fee.