Twitter Trending Tweets API — Explore an X Timeline
Use the Twitter Trending Tweets API to request a public trend timeline by language, region and optional topic. Inspect returned posts before organizing your own topic briefing.
1 credit per successful request, including empty results. Failures are free.
https://api.goanyapi.com/api/v1/twitter/trendingRun 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.
Choose the context before interpreting the posts
The Twitter Trending Tweets API requests a trend timeline by language, region and optional topic. An editorial researcher can keep returned post text, author handles and source links in a reading sheet, then draft an attributed topic briefing. Store the request conditions beside that material so colleagues understand the context used to gather it.
Request teaching: distinguish tweets from the saved labels
For a request exercise, use language set to en and placeId set to the empty string for the global selection. You may optionally supply topicId as a numeric string or a supported full topic URL. This explains the request; it is not a claim that the saved display came from those exact conditions. The historical response on this page contains 50 trend labels and regional metadata, with no tweets. It is not a trend tweet example, and it must not be rewritten as 20 posts. Inspect the full JSON and check which list actually exists before asking an Agent to summarize it. The trending documentation defines the POST contract.
- data.result.tweets[].text
- Read the original post wording here when a live result contains tweets. This intended field is absent from the historical sample; a trend label is not post text.
- data.result.tweets[].author.screen_name
- Keep each returned author handle beside its post in the reading sheet. The saved label sample has no author records, and a selected region does not establish author residence.
- data.result.tweets[].counts
- Retain the individual interaction measures from returned tweets. These give a reading sheet useful context for each post; missing counts should remain distinct from returned zero values.
- data.result.trends[].name
- The historical sample actually contains this label field, beginning with Steelers. Its accompanying tweetVolume is null. It supplies neither a tweet body nor a known volume for that entry.
- data.result.asOf
- This timestamp belongs to the regional metadata in the saved label structure. Keep it with that observation rather than assigning it as the publication time of a post.
A limited timeline request, not complete coverage
The public timeline request is limited to at most 20 records and has no pagination; fewer records may be returned. Do not send count, page_size or cursor. Language and region use separate enumerations, while the topic is optional. Successful requests, including successful empty results, use the current configured fee; failures are free. The 50-label historical sample is a structure mismatch, not an expanded tweet allowance or evidence of complete trend coverage.
Plan a useful reading workflow
Use returned timeline fields to assemble source notes, reading lists and topic briefings for your team.
Set a language context
A researcher can choose an allowed language, with English as the declared default. Store that selection in the briefing header so colleagues can understand the intended reading context when they inspect the returned posts.
Choose a supported region
A regional editorial desk can select a supported placeId or the global empty-string option. Pair the request selection with the result in its reading log, keeping a regional assignment attached to the material gathered.
Keep an optional topic explicit
An analyst with a known topic can provide its numeric ID or full topic URL. Put that topic reference in the assignment notes so the reading set is connected to the subject the analyst intended to explore.
Prepare an attributed reading sheet
When tweets are returned, an editor can collect text, handles, source links and individual interaction counts in a reading sheet. Add brief annotations beside selected records to prepare an attributed topic briefing.
Recognize label-shaped results
A data reviewer can identify a trends array before processing a response as posts. In the saved example, retain the 50 labels as a regional label observation and use the JSON to inspect their available metadata.
Ask for a constrained Agent brief
An HTTP-capable Agent can request the chosen context, inspect the actual structure and prepare notes from returned tweets. Configure authorization securely in the client and include the intended language, region and optional topic in its task.
Questions about scope, fields and requests
The saved historical result contains regional labels and no tweets array. It is displayed in its actual structure. It is not a 50-tweet example, a full 20-post guarantee or evidence that future results always have the same shape.
Language and placeId accept their listed enumeration values. Language defaults to en, and the empty placeId selection is global. The optional topicId accepts a numeric topic ID or a supported topic URL. It is a topic reference, not a region, and cannot replace placeId or WOEID.
No. The timeline contract requests at most 20 records and exposes no page size or cursor. The returned set may be smaller. Repeating a request is a new observation, not a supported continuation that guarantees additional unique posts or complete coverage.
No. This page concerns a trend tweet timeline by language, region and optional topic. Use the regional trends API for labels selected by WOEID, or the separate trending search timeline for its tag and timeFilter inputs. Neither distinction implies an unrestricted keyword or historical archive search.
Repeated calls are separate requests. Successful calls, including empty results, use the current configured rate; failures are free. A client can arrange a schedule and retain observations, but the API does not include an automatic monitoring subscription. Opening this page only loads its saved historical example.
Choose the next resource by the question you need to answer
Use this contextual timeline alongside individual post details, public author profiles or a separate trending search timeline. Each follow-up query is an independent request.