X API reference
Eight things we had to establish before writing any code
Everything here was checked against X’s own documentation on 2026-09-07, which matters more than usual: the tiers most articles still describe stopped accepting new signups in February 2026, and the pricing model that replaced them works differently enough to change how a product is built.
Why these pages exist
Costing out a bookmarks product means answering a short list of questions X does not answer in one place: what a read is billed as, how often you can afford to run, what the rate limits really constrain, and what you are obliged to do with content once you have stored it. We had to answer them to decide whether the product was viable at a consumer price, so the working is written up here rather than left in a private document.
One structural change drives most of it. On 6 February 2026 X closed its Free, Basic and Pro tiers to new signups and moved to prepaid credits spent per resource returned. Almost everything published before then — and a good deal published since — describes a system that no longer exists. That is why each page below carries a verification date and a link to its primary source on docs.x.com: X flags prices and caps as subject to change, and a dated page is honest about the possibility of being out of date.
| The number | Value | Where it comes up |
|---|---|---|
| Posts: Read | $0.005 per post object returned | Post read — and every cost estimate downstream of it |
| Owned Read | $0.001, conditional | Owned read — the condition excludes multi-tenant products |
| Deduplication window | 24-hour UTC day | Resource deduplication — sets the sync schedule |
| Bookmarks rate limit | 180 requests / 15 min, per user, no per-app limit | Bookmarks endpoint — why capacity is not the bottleneck |
| Monthly cap | 3,000,000 post reads per billing cycle | Pay-per-use — the point at which Enterprise starts |
max_results | 1 to 100, default 10 | Pagination — page size is the cost unit |
What it costs
Three pages that between them answer what reading a bookmark actually bills you for.
How the reading works
The endpoint, the cursor that walks it, and the rule that decides how often to run.
Bookmarks endpoint
GET /2/users/:id/bookmarks — the only compliant way to read someone's saved posts.
ReadPagination token
The opaque cursor that walks a bookmark list, and why it goes stale.
ReadResource deduplication
X charges once per resource per 24-hour UTC window, which decides how often syncing should run.
ReadPermission and obligations
Getting access to an account, and what you owe once you have stored its content.
Where this leads
If you are here to work out what a bookmarks tool costs to run, the cost calculator applies these rates to a library size in the browser. If you are here because you have bookmarks you want out of X, the export destination pages cover the file and what to do with it.