Twitter Tweet API — Read a Public X Post
Look up a public X / Twitter post by its ID or full status URL. Get the original text, author, interaction counts and available link previews in one structured result.
1 credit per successful request, including empty results. Failures are free.
https://api.goanyapi.com/api/v1/twitter/tweet/detailRun 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 shared post into a source note
The Twitter Tweet API fits a specific editorial task: someone shares a post, and you need its wording, attribution and supporting links together. Give GoAnyAPI the known resource rather than a search phrase. The result can become a row in your own source register, with the post URL, author handle and observation notes kept alongside the original text. Your application decides what to retain and how to present it; the API supplies the returned public record, not an editorial verdict about its claims.
Saved example: a ChineseWSJ news post
Use https://x.com/ChineseWSJ/status/2121105805487305093, or its numeric ID, as url. The saved response identifies ChineseWSJ and contains Chinese text about an American officer arrested in Britain. Its five interaction counts are 2 bookmarks, 11 likes, 0 quotes, 0 reposts and 1 reply; views is the string "14560". A news link preview is present, while media is an empty array and quoted is null. These observations describe that saved record, not current counters. In your own worksheet, pair the original wording with the expanded article link and a separate review note. See the tweet documentation for the POST request and authentication.
- data.result.author.screen_name
- Attribute the source to the returned handle, ChineseWSJ in this sample. Retain the author name and original ID alongside it in a publisher or source register.
- data.result.text
- Store the original wording, including its shortened link. Put translations and summaries in separate worksheet columns so readers can return to the source text.
- data.result.counts.favorite_count
- The saved like count is 11. Keep all five interaction measures in separate columns; the sample’s zero quotes and reposts are actual returned values.
- data.result.views
- The saved views value is a string. Preserve it in the original JSON and validate any numeric conversion used for a chart or spreadsheet.
- data.result.card.title
- This is the linked article’s title. Its image, domain and description provide context for an article-reading queue; attached post media is a separate field.
- data.result.links[].expanded
- Retain the expanded article address with the post reference. The sample’s quoted value is null, so the source note has no quoted post to attribute.
Keep the record and your interpretation separate
This is a public post lookup, with no pagination. It does not publish posts, search an archive or promise access to deleted or private content. Preserve null, empty strings, empty arrays and omitted fields as returned; they do not by themselves make the business result a failure. Each successful request, including a successful empty result, is charged at the current configured rate. Failed requests are free. Parsing a supported full status URL adds no separate charge.
Useful ways to work with a known post
Start with one source, then choose the output your team needs. The following records and summaries are assembled by you from the returned data.
Resolve a source from its link
Editors can submit the status link attached to a story and collect the available record. The X tweet details API places the post reference, text and author together for a source queue.
Attribute the original wording
Researchers can arrange author name, handle and ID beside the original text. A source table with these separate columns makes it easier for reviewers to identify which account published each statement.
Record separate interaction measures
Analysts can store likes, replies, reposts, quotes, bookmarks and views as separate observations. Add a retrieval date to the worksheet, then compare the same measure across records collected for the task.
Trace the referenced article
A reading assistant can place the returned card title, domain and expanded article address in a follow-up queue. Keep the post’s wording next to the article reference so both contexts remain available.
Distinguish previews from attachments
A content catalog can distinguish attached media from a linked article image. Read media and card separately, retain available addresses and show a fallback when an image cannot load.
Give an Agent a bounded reading task
An HTTP-capable Agent can use the public POST contract to read a specified post, then prepare an attributed source note. Configure authorization securely in the client and give it the exact resource link.
Questions about inputs, results and costs
Yes. Supply the numeric post ID or a supported full x.com or twitter.com status URL in the same resource input. This Twitter tweet lookup by ID also accepts that full link without a separate parsing charge. A profile address or shortened sharing link is not the required resource type.
The image belongs to the linked article card. The saved post has no attached media, and its quoted field is null. Those fields describe different parts of the response. Your interface should not manufacture a photo attachment or quoted author from the card image.
No. The initial display uses a saved response. An explicit query sends a request; successful results, including empty results, use the currently configured rate, while failures are free. Check the displayed fee before querying. Repeated lookups are separate requests, even for the same post.
An HTTP-capable Agent can make the public request and organize the result when you configure its credentials. Scheduling, retention and comparisons must be implemented in your client or workflow. Each new request is billed separately; the endpoint itself does not subscribe to changes or send alerts.
Add context after the post lookup
Use the Twitter Tweet API for the known source. Choose a profile lookup for account context or a trend timeline for a separate set of posts. Each additional successful request has its own configured charge.