Skip to main content
GET https://xquik.com/api/v1/x/bookmarks
Export Twitter bookmarks from one connected account. The route returns saved tweets, authors, likes, replies, reposts, views, media, and cursor checkpoints. The X (Twitter) developer reference defines bookmarks as private, authenticated-user content.
Requested result counts are upper bounds for paid authenticated calls. Remaining credits may not cover the full page or ID list. If so, 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
The route reads bookmarks through your connected X account. Without one, it returns 424 account_required. Use Connect X account to add one. When your connected X accounts are busy, it returns 503. Retry after the Retry-After delay. Folder reads need X Premium. For any other account, folderId returns 424 bookmark_folders_unavailable. Omit folderId to read all bookmarks.

Bookmarks handoff

Use GET /x/bookmarks when a caller needs saved tweets from the authenticated account. The caller can be a reading list, CRM, research queue, or agent. The examples write JSON Lines rows. Each row has bookmark source, folder ID, tweet ID, tweet URL, and text. It also has author ID, username, display name, follower count, and verified state. It also has profile image URL, engagement counts, media URLs, and cursor fields. Store the last saved next_cursor per folder. Resume each bookmark export from that checkpoint.

All saved tweets

Omit folderId when the workflow needs every bookmarked tweet visible to the connected account.

Folder export

Call Bookmark Folders first, then pass its folder_id as folderId. Folders need X Premium.

Cursor checkpoint

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

Account-scoped queue

Store saved-tweet rows only in systems scoped to that account.

Twitter bookmark API questions

How do I export Twitter bookmarks?

Run the Node.js or Python example for each cursor page. Both examples create a structured JSON Lines record for every saved tweet. Each row keeps tweet text, authors, likes, replies, reposts, and views. It also keeps media URLs and folder context. Convert the completed rows to a CSV file after collection. Use tweet_id as the stable key. Create a bookmarks page in a spreadsheet or research tool. Choose destination columns before sending rows to Notion databases or CRMs.

How does bookmark authentication work?

Connect the X account that owns the saved tweets. Include that account’s Xquik API key in every request. The endpoint never accepts another username. X treats bookmarks as private to their owner.

Can I export another user’s bookmarks?

No. Bookmarks are private to the connected account. Keep every export scoped to that account. Do not publish saved tweets or private folder names.

How do bookmark folders work?

Call Get bookmark folders first. Pass the returned folder_id as folderId. Omit folderId to request all visible bookmarks from the connected account. Store one next_cursor checkpoint per folder. Keep folder_id when importing records into Notion databases.

What limits a bookmark export?

You receive the bookmarks that the connected account can view. Low credits may reduce the returned row count. A 429 response includes retry guidance. 424 account_required means you have no connected X account. Other 424, 502 & 503 responses are temporary read failures.

How should I store a bookmark export?

Store the connected account ID beside each row. Keep private folder names out of public logs. Delete temporary files after the approved handoff finishes.

Query parameters

Which saved-feed endpoint?

Saved tweets

Use GET /x/bookmarks for bookmarked tweets from the connected account.

Bookmark folders

Use GET /x/bookmarks/folders to find folder IDs before a folder-specific bookmark export.

Home timeline

Use GET /x/timeline for the connected account’s home feed instead of saved tweets.

Notifications

Use GET /x/notifications for inbox activity rows from the connected account.

Headers

Response

200 OK

Response examples

200 example

  • 400 { "error": "invalid_input", "message": "Invalid input. Check the request body." }
  • 401 { "error": "unauthenticated", "message": "Authentication required. Provide a valid API key or bearer token." }
  • 402 { "error": "insufficient_credits", "message": "Insufficient credits. Top up or subscribe to continue." }
  • 403 { "error": "api_key_paused", "message": "This API key is paused. Resume it at dashboard.xquik.com/api-keys to use it again." }
  • 424 { "error": "x_api_unavailable", "message": "X data source temporarily unavailable. Try again later." }
  • 429 { "error": "rate_limit_exceeded", "message": "Too many requests. Try again later.", "retryAfter": 60 }
  • 502 { "error": "x_api_unavailable", "message": "X data source temporarily unavailable. Try again later." }
  • 503 { "error": "x_api_unavailable", "message": "Xquik is busy right now. Retry shortly." }