The official X API bookmarks endpoints require a developer account, pay-per-use billing, and an OAuth 2.0 user-context flow. Tweetsmash imports your bookmarks first, then serves them from your own library: one Bearer token, unrolled threads, label filters, and webhooks.
curl "https://api.tweetsmash.com/v1/bookmarks?limit=20" \
-H "Authorization: Bearer YOUR_API_TOKEN"Full reference, parameters, and response examples live in the API documentation. Prefer no-code? Tweetsmash also syncs bookmarks straight to Notion and Google Sheets.
A REST API at api.tweetsmash.com/v1 that returns the posts you bookmarked on X (Twitter) as JSON, with unrolled threads, author details, and your labels. It authenticates with a personal Bearer token that you generate in your Tweetsmash dashboard.
Yes. Tweetsmash imports your X bookmarks into your own library, and the API serves them from there. You do not need an X developer account, OAuth 2.0 setup, or pay-per-use API billing. One Bearer token is all it takes.
GET /v1/bookmarks fetches your saved posts with pagination and filters. GET /v1/labels lists your labels. POST /v1/labels/add and POST /v1/labels/remove manage labels on tweets. Webhooks can push new bookmarks to your own endpoint in real time.
100 requests per hour per API key. Responses include pagination cursors, so you can walk through your full bookmark archive within the limit.
Yes. The same API token powers the Tweetsmash MCP server, which lets Claude, ChatGPT, Cursor, and other MCP clients search, count, and label your X bookmarks through natural language.
