API Rate Limits
@twitterhelp · API Team
Learn how Twitter's API rate limits work to ensure fair usage and system stability. Understand your limits and how to handle them effectively.
Introduction to Rate Limits
Twitter API v2 uses rate limiting to prevent abuse and ensure equitable usage. Requests are grouped into resource families with specific limits based on your authentication type.
User Authentication
Rate limits per user token (Bearer + User ID)
App Authentication
Rate limits for app-level requests
Rate Limit Tiers
| Endpoint | User Tier | App Tier | Window |
|---|---|---|---|
| GET /2/tweets | 15/min | 450/min | 15 minutes |
| POST /2/tweets | 5/min | 200/min | 15 minutes |
| GET /2/users | 60/min | 900/min | 15 minutes |
Checking Your Limits
Use these response headers to monitor remaining limits:
x-rate-limit-limit: 15
x-rate-limit-remaining: 12
x-rate-limit-reset: 1726089600
x-rate-limit-limit
Maximum number of requests in the window
x-rate-limit-remaining
Number of remaining requests available
Best Practices
Caching Responses
Store responses locally to reduce redundant API calls. Twitter recommends using 15-minute cache windows.
Exponential Backoff
When 429 errors occur, delay retries with increasing wait times between attempts.