Rate Limits

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:

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.

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. Read your remaining credits from the account endpoints, which are free, and alert before you run dry.

Watching for a 402

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