The REST APIs provide programmatic access to read and write Twitter data. Create a new Tweet, read user profile and follower data, and more. The REST API identifies Twitter applications and users using OAuth; responses are in JSON format.
If your intention is to monitor or process Tweets in real-time, consider using the Streaming API instead.
Below are some documents that will help you get going with the REST APIs as quickly as possible
- API Rate Limiting
- API Rate Limits
- Working with Timelines
- Using the Twitter Search API
- Finding Tweets about Places
- Uploading Media
- Reference Documentation
Default entities and retweets¶
entities and retweets
are returned by default. Entities are returned as part of Tweet
objects unless the
include_entities parameter is set to
Native retweets are included in timelines unless the
parameter is set to
Authentication on all endpoints¶
Applications must authenticate all requests with OAuth 1.0a or Application-only authentication. This allows us to prevent abusive behavior, and it also helps us to further understand how categories of applications are using the API. We apply this understanding to better meet the needs of developers as we continue to evolve the platform.
The rate limit window is divided into 15 minute chunks per endpoint, with most individual calls allowing for 15 requests in each window. Be sure to read the Rate Limiting documentation as well as to review the per-method limits available here.
Twitter client policies¶
All applications replicating the core Twitter experience, usually called “clients”, must adhere to certain restrictions, including a 100,000 user token limit. To be clear, the 100,000 user token limit applies only to the small number of clients replicating the core Twitter experience - it does not apply to the majority of other applications in the broader ecosystem. These clauses are outlined in detail in the Developer Policy.