Twitter & X API Rate Limits: Current Endpoint Limits

X's current public pricing page does not list a general Free-tier allowance. Standard access is prepaid pay-per-use, with Post reads at $0.005 per resource and User reads at $0.010. Developers with older or private access should use the limits shown in their Developer Console. GetXAPI returns roughly 20 results per standard call at $0.001 with no monthly minimum.

On pay-per-use the filtered stream is limited to a single concurrent connection with the throughput constraints published in X's documentation, so the practical limit is connection count rather than a per-window request cap. If you need push delivery of new posts without holding a stream connection open, a webhook-based monitoring API is an alternative, because it pushes each new post to your endpoint without you handling reconnects and gap recovery.

Twitter API rate limits are caps on how many requests you can make per time window. Under the official X API pay-per-use model, rate limits vary by resource type and usage volume. GetXAPI has no endpoint-specific quota, though general service throttling still applies.

GetXAPI does not enforce endpoint-specific daily or 15-minute quotas, so there is no per-endpoint window to plan around. General service throttling still applies: under sustained high concurrency requests can return 429, so production clients should retry with exponential backoff just as they would against any API. Standard calls are $0.001; DM, Create Tweet, and premium calls are $0.002; complete-tweet calls are $0.003; and some specialized endpoints price separately.

They usually refer to the same constraint: request windows enforced by the official X API. Developers still search for Twitter API rate limits because the product was historically called Twitter, while X API limits is the newer naming. In practice, you should plan around endpoint-specific quotas, 429 responses, and monthly usage cost.

Official X API limits are primarily endpoint-specific and can vary by access level, operation type, and usage model. That means a search endpoint, user lookup endpoint, and write endpoint can each have different behavior. GetXAPI uses a simpler pay-per-call model with no endpoint-specific quota, though general service throttling still applies.

The most cited 24-hour limits are the app-level post-create cap of 10,000 per day (with a 100/15min user-context window underneath) and the 1,440-per-day DM send cap on user context. X publishes 24-hour windows on some GET endpoints too, so treat 24-hour caps as endpoint-specific rather than write-only, and read the per-endpoint reference for the exact window on each. On the read side, pay-per-use also carries a 3 million post-read monthly hard cap.

Recent search allows 450 requests per 15 minutes with a 7-day lookback. Full-archive search allows 300 requests per 15 minutes but also enforces a hard 1-request-per-second cap, and that per-second cap is what actually trips most integrations: you get a 429 while the 15-minute counter still shows headroom. Plan your retry budget against the per-second cap rather than the window, and space full-archive calls at least a second apart.

v1.1 is retired for new access, so v2 limits are effectively the limits. X API v2 uses two separate counters. Endpoint rate limits count requests, so a call returning 100 Posts uses one request from the endpoint window. Billing and the monthly cap count returned resources, so that same call counts as 100 Post reads. Teams that conflate the two under-budget the monthly cap and the bill.

The official X API now uses consumption-based pay-per-use pricing, while rate limits remain endpoint-specific. Common read limits range from 15 requests per 15 minutes for some user-auth endpoints to 10,000 requests per 15 minutes for user timelines. Reads start at $0.005 per resource for posts and lists, and writes/actions commonly cost $0.005-$0.200 per request depending on action type.

When you exceed the official X API rate limit, requests return a 429 Too Many Requests error and you wait until the window resets, using the x-rate-limit-reset header. GetXAPI has no per-endpoint window to exhaust, but sustained high concurrency can still return 429 from general service throttling, so keep a retry-with-backoff path in production clients either way.

Respect the x-rate-limit headers, keep request volume inside each endpoint's window, and retry only after the reset timestamp. The working patterns (retry code, exponential backoff with jitter, per-endpoint queues, proactive throttling) are covered in the 429 retry and backoff implementation guide. If your workload is sustained scraping, monitoring, or enrichment, GetXAPI removes the platform-level window planning entirely.

Yes for several endpoints. Post create caps at 10,000 per day at the app level (100/15min on user-context auth), and DM send caps at 1,440 per day on user context. 24-hour windows are most common on write endpoints, but X also publishes 24-hour limits on some GET endpoints, so check the per-endpoint reference rather than assuming only writes have daily caps. Read endpoints on pay-per-use are also hard-capped at 3 million post reads per monthly billing cycle before requiring Enterprise. GetXAPI has no endpoint-specific daily or monthly quotas, though general service throttling still applies.