Static endpoint reference · Basic Reads

Tweet lookup API endpoint reference

Look up one tweet by ID with enriched metrics, language, entities, and context fields.

Read the workflow guide →Browse the full API index →Compare endpoint costs →

GET/v1/tweets/{id}Basic ReadsFlat 1 credit#

Look up one tweet by ID with enriched metrics, language, entities, and context fields.

curl 'https://api.xfetch.io/v1/tweets/2055734812669865997' \
  -H "Authorization: Bearer $XFETCH_API_KEY"

Name	In	Type	Required	Constraints	Description
`id`	path	`string`	required	pattern: ^\d+$

Response

{
  "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
    }
  }
}

Context

From endpoint contract to working workflow

The commercial guide explains when to use this read, while this page keeps the request parameters, response example, schema, and code-derived pricing together. Both point back to the full reference index so the endpoint remains part of one documented API surface.

Twitter Search APIDiscover post IDs from a query before looking up a focal result.AI and MCP workflowsFeed normalized posts and richer context into an agent pipeline.Tweet context endpointContinue from the focal post into author, quote, and retweeter blocks.

From endpoint contract to working workflow

Run this endpoint in the dashboard playground