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

Workflow · Twitter timeline API

Twitter timeline API for repeatable account research

Page through a public account's recent original posts and reposts as normalized tweet records, with one continuation contract for repeatable reads.

Open endpoint reference →

Copyable request + contract response example

Timeline pages return normalized tweets plus continuation metadata

The example is sourced from the endpoint documentation manifest. A separate sibling endpoint includes replies when that broader activity view is required.

GET/v1/users/{id}/tweets
Basic Reads
cURL
curl 'https://api.xfetch.io/v1/users/44196397/tweets' \
  -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": 2,
      "remaining": 998
    },
    "pagination": {
      "next_token": "tok_2"
    }
  }
}

One workflow

Turn one account timeline into a repeatable research input

Use the timeline endpoint for recurring account intelligence, creator tracking, or ingestion jobs where chronological public activity is the useful unit.

  1. 01

    Pass the account's numeric user ID to the timeline path.

  2. 02

    Store the normalized tweet records your application needs.

  3. 03

    When a next token is present, pass it unchanged to fetch the next page.

Code-derived cost

Timeline cost follows the tweets returned

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

Current rule

1 base + 1 per item

Each successful page has a base component and an item component based on the number of tweet records returned.

Documented response example

2 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

Twitter Timeline API questions

What does the Twitter Timeline API include?
The endpoint on this page returns recent original tweets and retweets in reverse-chronological order as normalized tweet objects.
Are replies included in this timeline?
Not in this endpoint. Use the documented tweets/replies sibling when replies are part of the workflow.
How do I request the next timeline page?
Pass the opaque meta.pagination.next_token back as next_token. Do not parse it or combine it with a different account request.
How is a timeline page charged?
The current public rule combines a base amount with the number of tweets returned. The exact rule and sample charge shown here are derived from shared pricing code.

Run the documented workflow on your own key

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

Compare API costs →