Core mechanics · module 4 of 6 · 6 min read
The API and tooling
Why did your integrations break, and what does access cost now?
- API tiers
- rate limits
- third-party clients
- data access
- scheduling tools
Read first: Using X as a distribution channel
The API change is the most concrete, least ideological thing that happened to X, and it broke a great deal of tooling that marketers depended on.
What changed
Free API access was largely withdrawn and replaced with paid tiers. The free tier became effectively write-only at trivial volumes; meaningful read access moved to paid plans, with higher tiers priced for enterprises rather than practitioners.
What broke as a result
- Third-party clients shut down, in some cases with days of notice.
- Analytics tools lost historical and real-time data access, or repriced.
- Scheduling and social management tools kept limited posting but lost much of their listening and reporting.
- Academic and public-interest research on the platform largely stopped, which is why independent evidence about X is now thin — including evidence you might want when deciding whether to stay.
That last point is worth sitting with: the shortage of reliable data about X is partly a product decision, and it makes every claim about the platform harder to verify.
What it means practically
- Assume your reporting is partial. Cross-platform dashboards often show less for X than for other channels, and the gap is access, not activity.
- Budget for it if you need it. Real programmatic access is now a line item.
- Export what you care about. Anything you would want a history of should be pulled out rather than assumed to remain available.
- Prefer native analytics for what the platform will tell you about your own account, and treat third-party numbers with caution.
Rate limits
View limits and rate caps have been introduced and adjusted repeatedly, sometimes without notice. Anything automated against X should degrade gracefully rather than assume availability — the same defensive posture you would take with any dependency that changes unilaterally.
What trips people up
- Assuming a tool still works because it did last year.
- Comparing X metrics to other channels without noting the data is not equivalent.
- Building a workflow on an access tier that could be repriced.
You have got this when
You know what you would lose if X access changed again tomorrow, and whether you have a copy of it.
Go to the source
What has changed since
Stories from the briefs that touch this module.