Twitter Trending Search API — Read an X Trend Timeline
Use the Twitter Trending Search API to read a trend timeline. Inspect post text, author handles and available interaction counts, with optional tag and timeFilter inputs, then organize an attributed reading list.
1 credit per successful request, including empty results. Failures are free.
https://api.goanyapi.com/api/v1/twitter/trending/searchRun 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.
Turn a trend timeline into an attributed reading list
The Twitter Trending Search API gives an editor or community researcher a limited set of trend timeline posts to inspect. It is useful when the next step is reading the returned wording, recording sources and preparing your own summary of that set. The optional tag input belongs to this trend search context; its name does not establish support for searching any hashtag across X. Keep the request conditions and the actual returned records together, rather than treating the result as a complete conversation or a measure of public opinion.
Saved example: an AO3 status update among 20 records
The saved request example has no filters. Its response contains 20 tweets, including an AO3_Status post saying AO3 is back up, with some features temporarily disabled. The record has a publication timestamp, separate interaction counts, views as the string "7211595", an article card and an expanded link. Card description and quoted are null, and media is empty for that post. This illustrates the saved record, not a new search for AO3 or an up-to-date service announcement. In your own reading list, place the author and original text beside the source link, then add a separately labelled summary. See the trending search documentation for the public POST request.
- data.result.tweets[].author.screen_name
- The first saved record identifies AO3_Status. Retain the handle beside its text in the reading list so a summary can be traced back to the account that posted it.
- data.result.tweets[].text
- Read the body before summarizing the record. The AO3 status update and its card title use different wording; preserve both as separate context for a reviewer.
- data.result.tweets[].created_at
- This is the post publication timestamp. Keep your retrieval time separately when saving observations. It does not establish which timeFilter values correspond to a particular historical window.
- data.result.tweets[].counts.favorite_count
- The first saved post has 471,368 likes. Store this beside the other interaction counts. Sorting these records by likes would describe only the returned set.
- data.result.tweets[].views
- The first record returns views as a string. Preserve the original value and validate before numeric conversion. Other records in the saved list also show actual photos and video information.
Describe the set you received, not an unseen universe
Each request asks for at most 20 records, may return fewer, and has no pagination. Tag and timeFilter are optional strings; timeFilter has no declared default or enumeration of supported time windows. Do not invent dates, extra filters or a continuation cursor. Successful requests, including successful empty results, use the current configured rate, while failures are free. Keep nulls, empty arrays, empty strings and missing fields intact.
Six ways to organize returned trend posts
Turn the returned records into source notes and reading lists with your application or HTTP-capable Agent.
Keep trend filters in the task brief
A researcher can record optional tag and timeFilter inputs alongside the result. Including these conditions in a reading assignment helps colleagues understand the intended trend context when they revisit a saved set.
Draft an attributed digest
An editor can summarize returned post text and retain author handles and source links. A digest organized by these references allows reviewers to inspect the original wording before using the summary in their own report.
Separate the post from its references
A reading tool can collect expanded links and available card information into a follow-up queue. Keep the post text and card title separate, as the saved AO3 record demonstrates, to preserve their different contexts.
Compare measures within the response
Analysts can compare available likes, replies, reposts, quotes and bookmarks within the returned set. Retain individual counters in a worksheet and state which measure was used whenever the worksheet reorders the records.
Inspect actual media availability
A reviewer can distinguish posts with photos, video information, link previews or an empty media array. Retain available addresses and use image fallbacks while keeping the original post text readable.
Prepare a bounded reading assignment
An HTTP-capable Agent can make the public request and draft notes from its actual records. Configure authorization securely in the client and ask for a concise summary with author handles, publication times and source links.
Questions about scope, fields and requests
No. It is a trending search timeline with optional tag and timeFilter strings. The contract does not establish arbitrary keyword search, arbitrary hashtag retrieval, advanced search operators or full archive access. Choose this endpoint for its stated trend context and inspect the returned scope.
No such mapping is established by the public contract. The parameter is an optional string without a declared default or enum. Do not treat guessed labels as verified time windows. This page does not promise real-time delivery or a guaranteed date range for the returned posts.
No. Twenty is the maximum requested record count, not a promise of a full or stable response. The saved example contains 20 records, but another result may be smaller or empty. No page size or cursor input is provided, and repeated requests are not supported pagination.
Opening the page uses a saved response. Each explicit successful request, including a successful empty response, is charged using the current configuration; failures are free. If your Agent makes follow-up tweet or profile requests, each is billed separately. Review the displayed fee before starting the workflow.
Move from a trend record to a specific source
Use the Twitter Trending Search API for this timeline. Query an individual post or public account when you need separate context, or choose the language-and-region trend timeline for different inputs. Each additional request has its own configured fee.