READ API LIVEBuild on /v1 for search, profiles, timelines, audience graph, and tweet context.READ DOCS
xfetch

Workflow · Tweet lookup API

Tweet lookup API for one normalized post record

Turn a tweet ID into a stable record with text, author ID, an available timestamp, engagement metrics, language, entities, and public context fields.

Open endpoint reference →

Copyable request + contract response example

The response keeps post text, metrics, and entities in one record

The response example is generated from the endpoint docs manifest and its field names are backed by the public OpenAPI schema.

GET/v1/tweets/{id}
Basic Reads
cURL
curl 'https://api.xfetch.io/v1/tweets/2055734812669865997' \
  -H "Authorization: Bearer $XFETCH_API_KEY"
Response example
{
  "data": {
    "id": "2055734812669865997",
    "text": "These come from court transcripts",
    "author_id": "44196397",
    "created_at": "2026-05-16T19:39:07.000Z",
    "lang": "en",
    "conversation_id": "2055734812669865997",
    "possibly_sensitive": false,
    "like_count": 45028,
    "retweet_count": 9207,
    "reply_count": 2190,
    "quote_count": 236,
    "bookmark_count": 3116,
    "is_quote_status": true,
    "entities": {
      "hashtags": [],
      "urls": [],
      "mentions": []
    },
    "display_text_range": [
      0,
      33
    ],
    "quoted_tweet_id": "2055714457343471890"
  },
  "meta": {
    "request_id": "req_01HXFETCHEXAMPLE",
    "credits": {
      "charged": 1,
      "remaining": 999
    }
  }
}

One workflow

Resolve the post your application already knows about

Use single-tweet lookup after a search hit, webhook event, saved citation, or user-provided URL has already identified the post you need.

  1. 01

    Extract or store the tweet's numeric ID in your application.

  2. 02

    Call the single-tweet endpoint with bearer authentication.

  3. 03

    Use the normalized record directly or follow a related context workflow.

Code-derived cost

Single-tweet lookup uses the flat lookup rule

The rule and worked charge below come from the shared endpoint-pricing catalog used by billing and the API reference.

Current rule

Flat 1 credit

The endpoint returns one tweet object and maps to the single-object lookup pricing key.

Documented response example

1 credits

The example contains 1 primary record. Failed validation, authentication, insufficient-credit, rate-limit, service-side, and internal failures are not charged.

Estimate a monthly workloadSee every active pricing keySee the free starting credit grant

Related workflow context

Continue from this result

FAQ

Tweet Lookup API questions

What do I need to look up a tweet?
Pass the tweet's numeric ID in the path and authenticate with an xfetch API key.
What fields does tweet lookup return?
The normalized object includes the post ID, text, author ID, language, engagement counts, entities, available public context fields, and a created time when available, as described by OpenAPI.
When should I use tweet context instead?
Use single lookup for the focal post record. Use the tweet-context workflow when the job also needs the author, quote posts, and retweeters as named blocks.
How much does a tweet lookup cost?
It uses the public single-object lookup rule. The exact current amount on this page is read from the shared endpoint-pricing catalog.

Run the documented workflow on your own key

Google sign-in opens the dashboard playground with this endpoint selected.

Compare API costs →