TwitterAPIs Docs
Getting Started

Twitter API Rate Limits | Pay-Per-Call, No Quotas

TwitterAPIs has no platform rate-limit caps. You pay per call, so spend is the only ceiling. Be a good client.

TwitterAPIs does not impose platform rate-limit tiers. There is no 15-minute window, no per-endpoint request budget, and no monthly call ceiling to negotiate. You pay per call, so the only real ceiling is your credit balance.

The pay-per-call model

Instead of renting a quota, you pay for exactly what you use:

Call typePrice per call
Standard read$0.0008 (about 20 tweets)
Simple write (like, retweet, bookmark, follow, each undo, delete)$0.0008
Tweet creation, DM reads (dm/list, dm/conversation)$0.0016
Full tweet history (user/tweets/complete)$0.0024
Tweet thread (tweet/thread)$0.004

Bulk reads work out to roughly $0.04 per 1,000 tweets. New accounts start with $0.50 in free credits. There is no subscription and no monthly minimum, so a quiet week costs nothing. Your remaining credits and payment history live in the dashboard, not in a billable API call.

No throttle, real cost

Because there is no quota gate, a runaway loop spends real credits fast. Put a ceiling in your own code: cap total calls per job, and stop paging once you have the data you need.

Be a good client

No platform cap does not mean no limits worth respecting. A few habits keep your integration healthy and your spend predictable:

  • Handle 429 anyway. Bursts can still hit a momentary 429 during traffic spikes. Back off and retry. See Errors for a retry loop.
  • Cache what does not change. A user's profile or a settled tweet's text rarely moves. Cache it rather than refetching on every render.
  • Page only as far as you need. Each page is a billed call. Stop when you have enough.
  • Batch background jobs. Run large pulls off-peak and spread them out instead of firing thousands of calls in one tight burst.
  • Watch your balance. Track your remaining credits in the dashboard and top up before you run dry.

Watching for a 402

When credits run out, calls return 402 Insufficient credits rather than silently failing. Monitor your balance in the dashboard and top up before you hit zero, so a busy day never pauses your pipeline.

FAQ

Is there a rate-limit cap?

No. There is no platform rate-limit tier, no per-endpoint budget, and no monthly ceiling. You pay per call, so spend is the only real ceiling.

What does each call cost?

A standard read is $0.0008 for about 20 tweets, and simple writes (like, retweet, bookmark, follow, their undos, delete) are $0.0008 too; premium endpoints cost more (tweet creation and DM reads $0.0016, full tweet history $0.0024, tweet thread $0.004). Bulk reads work out to roughly $0.04 per 1,000 tweets.

Can I still hit a 429?

Occasionally, during traffic spikes. Back off and retry; a 429 is never billed, so the retry costs you nothing.

On this page