Twitter Rate Limits
X API v2 enforces rate limits on top of its pay-per-call pricing. Limits are scoped per endpoint with per-app (Bearer) and per-user (OAuth) buckets, typically over 15-minute or 24-hour windows. Headers expose the live limit, remaining, and reset timestamp. When a limit is exceeded, the API returns HTTP 429 with error code 88 ("Rate limit exceeded"); recovery is via the reset timestamp and exponential backoff.
Twitter Rate Limits is the machine-readable rate-limit profile for X (Twitter) on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 13 rate-limit definitions, measuring requests_per_15_minutes and requests_per_24_hours.
The profile also includes 5 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Social Media, Developer API, and Rate Limiting.
Limits
Policies
Sources
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for rate limits
4 MCP tools reach this
find_rate_limitsBrowse and filter every rate limit in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/twitter-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.