Skip to main content
GET
/
x
/
timeline
Get timeline
curl --request GET \
  --url https://xquik.com/api/v1/x/timeline \
  --header 'x-api-key: <api-key>'

Documentation Index

Fetch the complete documentation index at: https://docs.xquik.com/llms.txt

Use this file to discover all available pages before exploring further.

Requested result counts are upper bounds for paid authenticated calls. When remaining credits cannot cover the full page or ID list, Xquik returns fewer results. If zero paid results are affordable, it returns 402 insufficient_credits.
1 credit per result returned · All plans from $0.00012/credit
Requires a connected X account. Uses user-authenticated access.
curl https://xquik.com/api/v1/x/timeline \
  -H "x-api-key: xq_YOUR_KEY_HERE" | jq

# Page 2
curl -G https://xquik.com/api/v1/x/timeline \
  --data-urlencode "cursor=abc123" \
  -H "x-api-key: xq_YOUR_KEY_HERE" | jq

​
Home timeline handoff

Use GET /x/timeline when an inbox, CRM, monitor seed job, or agent needs the authenticated account’s home feed. The examples write JSON Lines rows with home timeline source, tweet ID, URL, text, author ID, username, display name, follower count, verified state, profile image URL, reply context, engagement counts, media URLs, seenTweetIds, and cursor fields. Store processed tweet IDs and pass them as seenTweetIds with the last saved next_cursor to reduce duplicates.

Home feed rows

Store one row per tweets[] item with timeline_source: "home" for the connected account.

Seen tweet dedupe

Add processed tweet IDs to seenTweetIds before requesting the next page.

Cursor checkpoint

Store has_next_page and next_cursor. Pass next_cursor back as cursor only when has_next_page is true.

Account-scoped sync

Keep home timeline rows in account-scoped inbox, CRM, monitor seed, or agent memory systems.

​
Query parameters

​
cursor
string
Pagination cursor. Pass the next_cursor value from the previous response to fetch the next page.
​
seenTweetIds
string
Comma-separated tweet IDs to exclude from results. Empty entries are ignored. Use this to avoid returning tweets the user has already seen.

​
Which timeline endpoint?

Home timeline

Use GET /x/timeline for the connected account’s home feed.

Profile timeline

Use GET /x/users/{id}/tweets for one public profile’s timeline.

Mentions timeline

Use GET /x/users/{id}/mentions for public mentions of one account.

Saved tweets

Use GET /x/bookmarks for tweets the connected account saved.

Notifications

Use GET /x/notifications for compact inbox activity rows.

Monitor events

Use List events after account or keyword monitors have captured replayable webhook events.

​
Headers

​
x-api-key
string
required
Your API key. Session cookie authentication is also supported.

​
Response

​
tweets
object[]
Array of timeline tweets.
​
has_next_page
boolean
Whether more results are available.
​
next_cursor
string
Opaque cursor for the next page. Empty string when no more results.
{
  "tweets": [
    {
      "id": "1893456789012345678",
      "text": "Timeline tweet content",
      "createdAt": "2026-02-24T10:00:00.000Z",
      "likeCount": 200,
      "retweetCount": 50,
      "replyCount": 15,
      "url": "https://x.com/user/status/1893456789012345678",
      "author": {
        "id": "44196397",
        "username": "elonmusk",
        "name": "Elon Musk",
        "followers": 150000000,
        "verified": true,
        "profilePicture": "https://pbs.twimg.com/profile_images/example.jpg"
      }
    }
  ],
  "has_next_page": true,
  "next_cursor": "DAADDAABCgABF..."
}
Related: Notifications · Bookmarks
Last modified on May 25, 2026