# Twitter Rate Limit Exceeded: Causes, Fix and X API Caps Canonical: https://www.twitterapis.com/twitter-api-rate-limits Description: Twitter rate limit exceeded? Why you see it, how long it lasts (15 min-24 hrs), and the per-endpoint X API caps. Fixes for users and developers. Generated: 2026-09-14T03:00:37.774Z --- 1. [Home](/) 2. / Rate Limits RATE LIMITS # Twitter Rate Limits: Exceeded Errors, API Caps and 429 Fixes What are Twitter (X) API rate limits and how do you avoid them? Twitter rate limits are per-endpoint request caps enforced by the X API that return a 429 error when exceeded. The official X API enforces 15-minute and 24-hour windows on every endpoint. TwitterAPIs is an alternative with a single ceiling of 600 requests per minute and 20 concurrent per key, so throughput scales at $0.0008 per call (source: twitterapis pricing) with one number to plan around instead of a per-endpoint matrix. This guide covers both the end-user "Rate limit exceeded" message and developer API caps. [ Regular Twitter / X user "Rate limit exceeded" explained You got the "Rate limit exceeded" message while browsing X. Why it happens, how long it lasts, and what to do -> ](#regular-user)[ Developer building on the API Twitter / X API rate limits reference Per-endpoint caps, 429 handling, headers, and how to skip platform-level rate limits with TwitterAPIs -> ](#developer-api) ## What Does "Rate Limit Exceeded" Mean on Twitter? When Twitter / X shows you the message **"Rate limit exceeded"** (or **"You are rate limited"**), it means you've made too many requests to Twitter's servers in a short period of time. This can happen even if you're just browsing, refreshing your timeline aggressively, scrolling rapidly through search results, or hitting many profiles in quick succession all count toward the limit. **How long does the Twitter rate limit last?** For regular users, the rate limit usually clears within **15 to 30 minutes**. In some cases (especially during platform-wide load spikes or if the system flags repeated automated patterns) it can last several hours. There's no way to manually reset it, the only fix is to wait it out. **Why does Twitter rate limit regular users?** Twitter applies rate limits to every user (logged in or not) to prevent abuse, scraping, and infrastructure overload. Common triggers: - Refreshing the timeline or notifications too frequently - Scrolling through long search-result pages quickly - Visiting many profiles in a short period - Logging in/out repeatedly - Using a third-party Twitter client that polls aggressively - Sharing an IP with many other Twitter users (e.g. corporate networks, public Wi-Fi) **What to do when you see "Rate limit exceeded":** 1. Stop refreshing, every refresh extends the cooldown. 2. Wait 15-30 minutes before trying again. 3. If you're using a third-party Twitter app, switch to the official X app or website to verify the issue isn't client-specific. 4. Check [Downdetector](https://downdetector.com/status/twitter/) or [@Support](https://x.com/Support) for platform-wide outages, sometimes "rate limited" is misreported during incidents. 5. If it persists for hours, log out, clear your browser cookies, and log back in. If you're a developer building against the Twitter API, the rate limit you're seeing is different, it's an [endpoint-specific quota with explicit headers](#developer-api) that you can read and respond to in code. Jump to that section for the full developer reference. ## "Rate Limit Exceeded" on X: Posting and Read Limits for Unverified Accounts (2026) Since the Twitter-to-X rebrand, the same **"rate limit exceeded"** message now appears under the X branding, and X applies different daily caps depending on whether your account is verified (X Premium / blue check) or unverified. If you're seeing the limit while just reading or posting normally, your account tier is usually the reason. **X posting and read limits by account type (2026):** Account type Posts read / day Posts published / day Verified (X Premium) ~10,000 2,400 Unverified ~1,000 2,400 (≈100/30min) New unverified (<30 days) ~500 Lower, anti-spam throttled These platform-level caps are set by X and change periodically, and they are separate from the developer X API quotas covered below. There is no way to raise the unverified limit other than subscribing to X Premium or waiting for the daily window to reset. **How to fix "rate limit exceeded" on X:** wait for the daily/15-minute window to reset (it does not roll over), stop refreshing during the cooldown, and if you rely on high-volume reads for a product or research workflow, move that traffic to an API instead of the consumer app. A developer-grade API like TwitterAPIs has **one flat ceiling of 600 requests a minute per key**, so account verification status never throttles your data pulls. TwitterAPIs One flat 600 req/min ceiling Throughput depends on your usage and system constraints, not endpoint-level throttle windows. Pay per call at a flat $0.0008 (~20 tweets). Official X API (Pay-Per-Use) Endpoint-specific limits Under the pay-per-use model, limits still apply per endpoint and per auth context. Post reads start at $0.005 per resource, user reads at $0.010, and content create is currently listed at $0.015 per request. ## Endpoint Rate-Limit Comparison AllTweetsUsersDMsListsBookmarksSpacesOther Showing 25 of 25 rows Family Endpoint Official X API TwitterAPIs Notes Tweets `GET /2/tweets` 3,500/15min app; 5,000/15min user 600 req/min per key \- Tweets `GET /2/tweets/:id` 450/15min app; 900/15min user 600 req/min per key \- Tweets `GET /2/tweets/search/recent` 450/15min app; 300/15min user 600 req/min per key 100 max results Tweets `GET /2/tweets/search/all` 1/sec; 300/15min app 600 req/min per key 500 max results Tweets `POST /2/tweets` 10,000/24hrs app; 100/15min user 600 req/min per key Official content create: $0.015/request Users `GET /2/users` 300/15min app; 900/15min user 600 req/min per key \- Users `GET /2/users/:id` 300/15min app; 900/15min user 600 req/min per key \- Users `GET /2/users/by` 300/15min app; 900/15min user 600 req/min per key \- Users `GET /2/users/by/username/:username` 300/15min app; 900/15min user 600 req/min per key \- Users `GET /2/users/:id/tweets` 10,000/15min app; 900/15min user 600 req/min per key \- Users `GET /2/users/:id/mentions` 450/15min app; 300/15min user 600 req/min per key \- Users `GET /2/users/me` 75/15min user 600 req/min per key \- DMs `GET /2/dm_events` 15/15min user Not offered DM Event: Read at $0.010/resource on the official X API DMs `GET /2/dm_events/:id` 15/15min user Not offered \- DMs `POST /2/dm_conversations` 1,440/24hrs app; 15/15min user Not offered DM Interaction: Create at $0.015/request on the official X API DMs `POST /2/dm_conversations/:id/messages` 1,440/24hrs app; 15/15min user Not offered DM Interaction: Create at $0.015/request on the official X API Lists `GET /2/lists/:id` 75/15min app; 75/15min user 600 req/min per key \- Lists `GET /2/lists/:id/members` 900/15min app; 900/15min user 600 req/min per key \- Lists `GET /2/lists/:id/tweets` 900/15min app; 900/15min user 600 req/min per key \- Lists `POST /2/lists` 300/15min user 600 req/min per key \- Bookmarks `GET /2/users/:id/bookmarks` 180/15min user 600 req/min per key \- Bookmarks `POST /2/users/:id/bookmarks` 50/15min user 600 req/min per key \- Spaces `GET /2/spaces` 300/15min app; 300/15min user 600 req/min per key \- Spaces `GET /2/spaces/search` 300/15min app; 300/15min user 600 req/min per key \- Other `GET /2/usage/tweets` 50/15min app 600 req/min per key \- Source: [developer.x.com/#pricing](https://developer.x.com/#pricing) and [docs.x.com/x-api/fundamentals/rate-limits](https://docs.x.com/x-api/fundamentals/rate-limits). X publishes specific per-app and per-user windows by endpoint, and its pricing docs list current pay-per-use read/write costs. TwitterAPIs endpoint and pricing claims are based on [docs.twitterapis.com/docs](https://docs.twitterapis.com/docs). Values last researched on May 5, 2026. ## Understanding the Three Twitter API Rate Limit Windows Twitter API rate limits are not enforced through one global cap. The official X API uses three different time windows depending on the endpoint and operation type. Knowing which window applies to your call is the difference between a clean retry and an avoidable 24-hour stall. - **15-minute windows.** The most common pattern. Counters reset every 15 minutes from your first request in that window. Tweet search, user lookups, and most read endpoints use this. If you hit the cap, the `x-rate-limit-reset` header tells you the unix timestamp when your bucket refills. - **24-hour daily caps.** Used for write-heavy endpoints, post create caps at 10,000/day at the app level, DM send caps at 1,440/day. These do not roll over; if you blow through your daily quota at 9am UTC, you are locked out until UTC midnight. - **1 request/second hard floor.** The full-archive search endpoint (`/2/tweets/search/all`) enforces a hard 1 req/sec ceiling on top of its 300/15min window. Bursting past this triggers an immediate 429 even when your 15-minute counter still has room. A common engineering mistake is to track only the 15-minute windows in your retry logic and ignore the daily caps. A scheduled scraper that runs hourly can pass every 15-minute check and still hit the daily ceiling at 4pm UTC, surfacing as "429s for no reason" in your logs. Plan retry budgets against the lowest of the applicable windows for each endpoint, not just the most visible one. ## Twitter API Rate Limits: TwitterAPIs vs twitterapi.io vs Official X API A side-by-side look at how the three most-compared Twitter API options handle rate limits in practice. Aspect TwitterAPIs twitterapi.io Official X API Platform-level cap None Per-credit, no time window 15-min and 24-hour, by endpoint 429 responses Not enforced at platform level Only when credits are exhausted Common; need retry logic Daily ceilings None None 10,000/day post create; 1,440/day DM Monthly hard cap None None 3M post reads on PPU; Enterprise above Reset-time visibility N/A Credit balance in dashboard `x-rate-limit-*` response headers Upstream X throttling Absorbed in the fetch layer Not published It is the upstream; limits are its own What bounds throughput Credit balance and capacity Credit balance A published per-endpoint window Engineering effort Single Bearer header, no scaffolding Track credit balance Per-endpoint queues, retry, backoff For the full pricing context behind these limits, see the [Twitter API cost guide](/blogs/twitter-api-cost) and the live [cost calculator](/twitter-api-cost-calculator). For the plain-language version of what a 429 is telling you, and how it differs from a 403, see [what rate limited means on Twitter](/answers/what-does-rate-limited-mean-on-twitter). ## What We Cap, What We Do Not, and What X Still Enforces Upstream Every table above compares the official X API's per-endpoint windows against one flat number. Claims about rate limits get used loosely across this market, so here is exactly what TwitterAPIs enforces, including the parts that are not a selling point. What we enforce One ceiling per API key: 600 requests per minute and 20 concurrent requests in flight. Past either one you get a 429 with a Retry-After header. That is the whole of it. No 15-minute bucket, no per-endpoint quota, no daily or monthly read cap, no tier to upgrade into. X still enforces upstream X applies its own limits to the data sitting behind every third-party provider, this one included. We absorb that pressure inside the fetch layer instead of passing a quota down to you. It surfaces as ordinary request latency, or in the rare case a fetch cannot complete, a standard HTTP error you retry. What actually bounds you Your credit balance, since every call bills at $0.0008. The per-endpoint page size, so a 50,000-tweet job is a cursor loop rather than one request. And our capacity, which scales with sustained load instead of resetting on a clock. **We do return rate-limit headers, under different names.** Every response carries `X-RateLimit-Limit`, `X-RateLimit-Remaining` and `X-RateLimit-Reset`, and a 429 adds `Retry-After` in whole seconds. Note the spelling: X uses `x-rate-limit-remaining`, we use `X-RateLimit-Remaining`, so retry logic ported off the official API needs the header names swapped rather than deleted. Keep the backoff branch, point it at Retry-After, and budget the rest by call volume and account balance. **One ceiling is not the same as unlimited.** Any provider selling unlimited is selling a slogan. Physics did not stop: a sustained multi-thousand-request-per-second burst is bounded by infrastructure here the same way it is bounded everywhere, and our own 600-per-minute ceiling sits under that. The practical difference is how many numbers you have to schedule around. On the official X API it is a different published window per endpoint per tier. Here it is one number that does not change when you switch routes, plus your budget. One more thing worth saying out loud, because the rest of this page is a comparison and comparisons tend to flatter whoever wrote them: if your workload is small enough to sit inside the official X API windows and you need a contract directly with X Corp, the windows are not your problem and this page has not made a case against them. One flat ceiling earns its keep on bursty, high-volume, read-heavy work, live event monitoring, backfills, follower-graph traversal, where the published window is the thing that stops the job. ## X API Rate-Limit Headers Cheat Sheet Every official X API response includes rate-limit headers that let you detect throttling before it triggers a 429. Production code should read these on every response, not just on errors. Header Meaning How to use it `x-rate-limit-limit` Total requests allowed in this window Set this as the budget for your queue `x-rate-limit-remaining` Requests left before throttling Throttle proactively when remaining drops below your batch size `x-rate-limit-reset` Unix timestamp when the window refills Sleep until this value, not a fixed delay Sleeping until `x-rate-limit-reset` beats a static `setTimeout`, it accounts for the actual reset window rather than guessing. TwitterAPIs returns the same information under X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset, plus Retry-After on a 429, so the same branch works after a header rename. ## How to Read X API Limits in Practice Most teams do not hit Twitter API rate limits evenly. They hit them in bursts: a search job fans out across many keywords, a user enrichment queue wakes up after an import, or a dashboard refreshes the same account list every few minutes. That is why the important question is not only "what is the listed endpoint limit?" but also "how much coordination does my app need before it can make the next request?" With the official X API, each high-volume workflow needs guardrails. Keep separate queues for search, tweet lookup, user lookup, and write operations. Track retry timestamps from 429 responses. Cache profile and tweet objects that multiple jobs reuse. For background jobs, store the next eligible run time instead of letting workers repeatedly fail against the same endpoint window. TwitterAPIs is simpler for teams that care more about throughput and cost predictability than managing endpoint windows. It charges by call, starts at $0.0008 per request, and has no platform-level rate cap. That makes it easier to model jobs by dataset size: 20,000 tweets is roughly 1,000 calls, 100,000 tweets is roughly 5,000 calls, and 1 million tweets is roughly 50,000 calls. ## Planning Checklist - Separate read-heavy jobs from write operations so one queue cannot block the other. - Cache stable user objects, profile lookups, and tweet metadata before retrying the same endpoint. - Budget by calls, tweets returned, and empty-result searches, not only by monthly account limits. - Add retry logic for 429 responses before launching scheduled collection jobs. - Use a cheaper Twitter API alternative when your workload is mostly search, timelines, user lookups, or enrichment. ## Rate-Limit Handling Examples If you stay on the official X API, build around 429 responses. If you use TwitterAPIs, the same data collection job can usually be modeled as a simple pay-per-call loop. Official X API retry (Node)Official X API retry (Python)Official X API retry (curl)TwitterAPIs request (Node) Copy ``` async function fetchWithRateLimit(url: string, token: string) { const response = await fetch(url, { headers: { Authorization: `Bearer ${token}` }, }); if (response.status === 429) { const resetAt = Number(response.headers.get("x-rate-limit-reset")) * 1000; const waitMs = Math.max(resetAt - Date.now(), 30_000); throw new Error(`Rate limited. Retry after ${waitMs}ms`); } if (!response.ok) { throw new Error(`X API request failed: ${response.status}`); } return response.json(); } ``` ## Common X API Rate-Limit Mistakes - **Treating all rate limits as 15-minute windows.** Daily caps on write endpoints are easy to miss. A nightly job that posts 200 tweets fits the 15-min window but breaches the 10,000/day app limit if it runs across many connected accounts. - **Sharing one Bearer token across multiple workers.** The cap is per app, not per process. Three workers hitting the same endpoint share one bucket and 3x your effective burst rate. If you need parallelism, split workers across distinct apps. - **Retrying 429s without backoff.** Hammering a throttled endpoint with sub-second retries can extend the soft penalty into something longer. Always sleep until the reset header value before retrying. - **Ignoring empty-result charges.** The official X API charges for searches that return zero results, and consumes the rate-limit slot too. Caching the queries themselves (not just results) avoids paying for the same empty search twice. - **Assuming auth context does not matter.** User-context (OAuth user) limits and app-context (Bearer) limits are separate buckets on the same endpoint. Mixing both can mask the true cap until you graduate to higher volume. ## Where This Fits in Your API Decision Rate limits are only one part of the buying decision. If you are choosing a Twitter data provider, compare limits together with price per 1,000 tweets, endpoint coverage, authentication, and how much work your team needs to do before data is usable. Start from the [TwitterAPIs homepage](/) for the product overview, then use the [Twitter API pricing comparison](/twitter-api-pricing) to map request volume to monthly spend. If you are comparing vendors directly, read [TwitterAPIs vs twitterapi.io](/twitterapis-vs-twitterapi-io) and [TwitterAPIs vs TweetAPI](/twitterapis-vs-tweetapi). For official-account setup context, the guides on [Twitter API v2 vs TwitterAPIs](/blogs/twitter-api-v2-vs-twitterapis) and [how to get a Twitter API key](/blogs/how-to-get-twitter-api-key) help explain when the official route still makes sense. If you need rate-cap-free Twitter data inside an AI agent, [the MCP server](/mcp) exposes all endpoints as native tools inside Claude or Cursor with no REST wrapper code. ### Skip the Rate-Limit Headaches TwitterAPIs runs one flat ceiling of 600 requests a minute per key and a 30-second signup. $0.0008 a call, about $0.04 per 1,000 tweets on full 20-tweet pages, $0.50 in free credits. [Get API Key](/twitter-api-key)[View pricing](/pricing) By the numbers ## Twitter rate limits, in numbers. Sourced caps behind the tables above. - Most official X API read endpoints reset on 15-minute windows, and full-archive search adds a hard 1 request per second floor. [(X API docs, 2026)](https://docs.x.com/x-api/fundamentals/rate-limits) - The official X API caps post creation at 10,000 per day at the app level and direct-message sends at 1,440 per day. [(X API docs, 2026)](https://docs.x.com/x-api/fundamentals/rate-limits) - Official X API pay-per-use is hard-capped at 3 million post reads per monthly billing cycle before Enterprise pricing applies. [(X Developer Platform, 2026)](https://developer.x.com/#pricing) - TwitterAPIs enforces one flat ceiling of 600 requests per minute and 20 concurrent per key, so throughput scales by call volume at $0.0008 per call, about $0.04 per 1,000 tweets. [(TwitterAPIs pricing, 2026)](/pricing) - A new TwitterAPIs account starts with $0.50 in free credit, roughly 12,500 tweets, with no daily or monthly window to plan around. [(TwitterAPIs pricing, 2026)](/signup) ## Frequently Asked Questions ### What does "Rate limit exceeded" mean on Twitter? If you're a regular Twitter / X user, "Rate limit exceeded" means you've made too many requests to Twitter's servers in a short period, usually triggered by aggressive refreshing, rapid scrolling through search results, or visiting many profiles quickly. It typically clears within 15-30 minutes; the only fix is to wait. If you're a developer hitting this on the API, it's the per-endpoint 429 response, see the rate-limit table above for endpoint-specific caps and the headers cheat sheet for handling it in code. ### Why am I rate-limited on Twitter as a regular user? Twitter applies rate limits to every user (logged in or not) to prevent abuse, scraping, and infrastructure overload. Common triggers include refreshing the timeline too often, scrolling through long search results quickly, visiting many profiles in succession, logging in/out repeatedly, using a third-party Twitter client that polls aggressively, or sharing an IP with many other Twitter users (e.g. corporate networks, public Wi-Fi). The limit isn't per-account, it's per-IP and per-session, so even read-only browsing can trigger it. ### What are X's rate limits for unverified accounts in 2026? As of 2026, unverified (non-Premium) X accounts are capped at roughly 1,000 post reads per day and about 2,400 posts published per day (about 100 every 30 minutes). New unverified accounts under 30 days old are throttled further by anti-spam systems, often to around 500 reads/day. Verified X Premium accounts get roughly 10x the read allowance. These platform caps are separate from the developer X API quotas. For programmatic access that does not move with your account, a third-party API like TwitterAPIs applies one flat ceiling of 600 requests per minute and 20 concurrent per key, the same whether the account you are reading is verified or not. ### What are Twitter API rate limits? 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. TwitterAPIs applies one ceiling instead: 600 requests per minute and 20 concurrent per API key, identical on every route. ### Does TwitterAPIs have rate limits? Yes, one: 600 requests per minute and 20 concurrent requests per API key. It is the same number on every route, so there are no tiered endpoint windows to model, and going over returns 429 with a Retry-After header. Every endpoint uses flat pay-per-call pricing at $0.0008 per request (~20 tweets per call). ### What is the practical difference between X API limits and Twitter API rate limits? 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. ### Do X API limits apply per endpoint or across the whole account? 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. TwitterAPIs uses a simpler pay-per-call model with one ceiling of 600 requests per minute per key across all of them. ### Does TwitterAPIs return rate-limit response headers? Yes, under different names. Every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset, and a 429 adds Retry-After in whole seconds. The official X API spells the same idea x-rate-limit-limit, x-rate-limit-remaining and x-rate-limit-reset, so retry logic ported off it needs the header names swapped rather than deleted. Read Retry-After on a 429, watch X-RateLimit-Remaining against the 600-per-minute ceiling, and budget the rest by call volume and credit balance at $0.0008 per call. ### So what actually bounds throughput on TwitterAPIs? Four things. First, the per-key ceiling of 600 requests a minute and 20 concurrent, the one published number here. Second, your account credit balance, since every call bills at $0.0008 and a zero balance stops the calls. Third, the per-endpoint page size: a search call returns a page of results, so a 50,000-tweet job is a cursor loop rather than a single request. Fourth, our own capacity, which scales with sustained load instead of resetting on a clock. ### What is the X API daily limit? Daily limits apply to write endpoints. The app-level post-create cap is 10,000 per 24 hours, with a 100/15min user-context window underneath. Direct messaging is capped at 1,440 sends per 24 hours. Read endpoints use 15-minute windows instead, the closest read-side daily-style limit is the 3 million post-read monthly hard cap on pay-per-use. ### How long does the Twitter rate limit last? For regular Twitter users, the rate limit usually clears in 15-30 minutes. In rare cases (heavy platform load or repeated automated patterns) it can last several hours. There's no way to manually reset it, wait it out, and avoid refreshing during the cooldown since that extends it. For developers on the X API, rate-limit windows are explicit: most endpoints reset every 15 minutes, write endpoints reset every 24 hours, and the exact reset time is in the x-rate-limit-reset response header. ### What does "rate limit exceeded" mean on X (not Twitter)? It's the same message under the new X branding. Since the rebrand, X shows "rate limit exceeded" or "you are over the daily limit" when you exceed the platform caps on reading or posting. The caps depend on your account type: verified (X Premium) accounts can read roughly 10,000 posts/day, unverified accounts roughly 1,000/day, and brand-new unverified accounts even less. The fix is the same: wait for the window to reset, or subscribe to X Premium for the higher tier. ### How do I fix "rate limit exceeded" on X? For the consumer app: stop refreshing (it extends the cooldown), wait for the daily or 15-minute window to reset since it doesn't roll over, and consider X Premium if you regularly hit the unverified-account cap. For a product, bot, or research workflow that needs high-volume reads, don't fight the consumer caps at all; pull the data through an API. TwitterAPIs returns tweets, profiles, and followers at $0.0008 per call under one flat ceiling of 600 requests per minute per key, so verification status never throttles you. ### How do official X API rate limits work under pay-per-use? 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. ### What happens when you hit a Twitter API rate limit? When you exceed the official X API rate limit, requests return a 429 Too Many Requests error. You must wait until the rate limit window resets before making more calls. TwitterAPIs also answers 429, but only above 600 requests per minute or 20 concurrent requests on one key, and the response carries a Retry-After header with the exact wait in seconds. ### How should I avoid 429 errors when using the official X API? Use a shared queue per endpoint, respect rate-limit reset headers when they are present, retry with exponential backoff, and cache repeated user or tweet lookups. If you need sustained scraping, monitoring, or enrichment workflows, TwitterAPIs removes the platform-level window planning and lets you scale by call volume. ### Is there a Twitter API rate limit per day? Yes for write operations. Post create caps at 10,000 per day at the app level (100/15min on user-context auth), DM send caps at 1,440 per day. Read endpoints don't have explicit daily caps but pay-per-use is hard-capped at 3 million post reads per monthly billing cycle before requiring Enterprise. TwitterAPIs has no daily or monthly cap at all; the only ceiling is the per-minute one, 600 requests per minute and 20 concurrent per key. ### What happens when X throttles the upstream data source? X enforces its own limits on the data behind every third-party provider, this one included. We absorb that upstream pressure inside the fetch layer rather than passing a quota down to the caller, so it surfaces as ordinary request latency, or in the rare case a fetch cannot complete, a standard HTTP error you retry. What it does not surface as is a per-endpoint quota you have to model in your own scheduler, which is the difference between absorbing an upstream limit and republishing one. ### Is one flat ceiling the same as unlimited? No, and a provider selling unlimited is selling a slogan. What we mean is that there is one number rather than a matrix of them: 600 requests per minute and 20 concurrent per key, the same on every route, with no 15-minute bucket and no per-endpoint quota. A sustained multi-thousand-request-per-second burst is still bounded by infrastructure here the way it is on any API, and our own per-minute ceiling sits under that. The practical difference is how many numbers you schedule around. On the official X API it is a different published window per endpoint per tier. Here it is one number plus your budget. ## Next read Continue exploring related pages: [ Twitter API v2 pricing vs TwitterAPIs Side-by-side endpoints, pricing, auth, and response shape, same data, 100x cheaper. ](/twitter-api-pricing)[ Twitter API cost calculator Estimate monthly spend using your request volume. ](/twitter-api-cost-calculator)[ How to get a Twitter (X) API key Step-by-step walkthrough of the X developer console, plus a 30-second alternative with $0.50 in free credits. ](/twitter-api-key) [View API Docs](https://docs.twitterapis.com)[Start Free](/signup?utm_source=aio&utm_medium=organic&utm_campaign=aeo-twitter-api-rate-limits) [ TwitterAPIs ](/) The cheapest pay-as-you-go Twitter and X API. $0.0008 per call, which works out to $0.04 per 1,000 tweets on a full 20-tweet page. No subscriptions and no developer account. ## Product / API - [Pricing](/pricing) - [Cost Calculator](/twitter-api-cost-calculator) - [Rate Limits](/twitter-api-rate-limits) - [MCP Server](/mcp) - [Integrations](/integrations) - [Language Clients](/sdk) - [Changelog](/changelog) - [Status](/status) ## Developers - [Documentation](https://docs.twitterapis.com) - [API Reference](https://docs.twitterapis.com/docs/reference/search/tweet-advanced-search) - [User Info](https://docs.twitterapis.com/docs/reference/user-reads/user-info) - [User Tweets](https://docs.twitterapis.com/docs/reference/user-reads/user-tweets) - [Advanced Search](https://docs.twitterapis.com/docs/reference/search/tweet-advanced-search) - [Verified Followers](https://docs.twitterapis.com/docs/reference/follower-graph/user-verified-followers) ## Resources / Compare - [Answers](/answers) - [Reviews](/reviews) - [Free Tools](/tools) - [Twitter ID Finder](/tools/twitter-id-finder) - [Get a Twitter API Key](/twitter-api-key) - [Official X API Comparison](/twitter-api-pricing) - [Twitter API Use Cases](/twitter-api-usecases) - [Twitter API Alternatives](/twitter-api-alternatives) - [Twitter Unofficial API](/twitter-unofficial-api) - [Twitter Free API](/twitter-free-api) - [TwitterAPIs vs twitterapi.io](/twitterapis-vs-twitterapi-io) - [TwitterAPIs vs GetXAPI](/twitterapis-vs-getxapi) - [TwitterAPIs vs TweetAPI](/twitterapis-vs-tweetapi) - [TwitterAPIs vs TwexAPI](/twitterapis-vs-twexapi) - [TwitterAPIs vs RapidAPI](/twitterapis-vs-rapidapi) ## Legal - [About](/about) - [Security](/security) - [Trust](/privacy-and-data-handling) - [Terms of Service](/terms-of-service) - [Affiliates](/affiliates) - [Contact](/contact) - [Jobs](/jobs) © 2026 TwitterAPIs. All rights reserved. TwitterAPIs is an independent third-party API for developers and researchers. Not affiliated with, endorsed by, or sponsored by X Corp. All systems operational