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

Static endpoint reference · Basic Reads

Twitter timeline API endpoint reference

List a user's recent original tweets and retweets in reverse-chronological order.

GET/v1/users/{id}/tweetsBasic Reads1 base + 1 per item#

List a user's recent original tweets and retweets in reverse-chronological order.

curl 'https://api.xfetch.io/v1/users/44196397/tweets' \
  -H "Authorization: Bearer $XFETCH_API_KEY"
NameInTypeRequiredConstraintsDescription
idpathstringrequiredpattern: ^\d+$
next_tokenquerystringoptional
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": 2,
      "remaining": 998
    },
    "pagination": {
      "next_token": "tok_2"
    }
  }
}

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.

Run this endpoint in the dashboard playground

Sign in with Google to mint a key and open the documented endpoint selection.