| Document | Description |
|---|---|
| The Streaming APIs | Overview The set of streaming APIs offered by Twitter give developers low latency access to Twitter's global stream of Tweet data. A proper implementation of a streaming client will be pushed messages indicating Tweets and other events have occurred, without any of the overhead associated... |
| GET statuses/firehose | This endpoint requires special permission to access. Returns all public statuses. Few applications require this level of access. Creative use of a combination of other resources and various access levels can satisfy nearly every application use case. |
| POST statuses/filter | Returns public statuses that match one or more filter predicates. Multiple parameters may be specified which allows most clients to use a single connection to the Streaming API. Both GET and POST requests are supported, but GET requests with too many parameters may cause the request to be... |
| Streaming API request parameters | Use the following request parameters to define what data is returned by the Streaming API endpoints: delimited stall_warnings follow track locations count with replies delimited This parameter may be used on all streaming endpoints, unless explicitly noted. Setting this... |
| Connecting to a streaming endpoint | Overview Authentication Connecting Disconnections Stalls Reconnecting Connection churn Rate limiting Best practices Test backoff strategies Issue alerts for multiple reconnects Handle DNS changes User Agent HTTP Error Codes Overview Establishing a connection to the... |
| Document | Description |
|---|---|
| Error Codes & Responses | HTTP Status Codes The Twitter API attempts to return appropriate HTTP status codes for every request. It is possible to suppress response codes for the REST API. Code Text Description 200 OK Success... |
| Document | Description |
|---|---|
| GET trends/available | Returns the locations that Twitter has trending topic information for. The response is an array of "locations" that encode the location's WOEID and some other human-readable information such as a canonical name and country the location belongs in. A WOEID is a Yahoo! Where On Earth ID. |
| GET statuses/user_timeline | Returns the 20 most recent statuses posted by the authenticating user. It is also possible to request another user's timeline by using the screen_name or user_id parameter. The other users timeline will only be visible if they are not protected, or if the authenticating user's follow request was... |
| GET statuses/retweets_of_me | Returns the 20 most recent tweets of the authenticated user that have been retweeted by others. |
| GET statuses/retweeted_to_me | Returns the 20 most recent retweets posted by users the authenticating user follow. |
| GET statuses/retweeted_by_me | Returns the 20 most recent retweets posted by the authenticating user. |
| GET favorites | Returns the 20 most recent favorite statuses for the authenticating or specified user in the requested format. |
| GET statuses/retweeted_to_user | Returns the 20 most recent retweets posted by users the specified user follows. The user is specified using the user_id or screen_name parameters. This method is identical to statuses/retweeted_to_me except you can choose the user to view. |
| GET statuses/retweeted_by_user | Returns the 20 most recent retweets posted by the specified user. The user is specified using the user_id or screen_name parameters. This method is identical to statuses/retweeted_by_me except you can choose the user to view. Does not require authentication, unless the user is protected. |
| GET lists/statuses | Returns tweet timeline for members of the specified list. Historically, retweets were not available in list timeline responses but you can now use the include_rts=true parameter to additionally receive retweet objects. |
| Document | Description |
|---|---|
| GET oauth/authenticate | Allows a Consumer application to use an OAuth request_token to request user authorization. This method is a replacement of Section 6.2 of the OAuth 1.0 authentication flow for applications using the callback authentication flow. The method will use the currently logged in user as the account for... |
| Connecting to Twitter API using SSL | The preferred method of connecting to the Twitter API is over HTTPS. While both HTTPS and Non-HTTPS connections to the Twitter API are supported, communicating over SSL preserves user privacy by protecting information between the user and the Twitter API as it travels across the public Internet... |
| Document | Description |
|---|---|
| What do I do if my account is compromised, hacked, or used outside of my control? | If you're having any questions about the security of your account, please contact @Support through our Support Center at https://support.twitter.com/forms/hacked -- we cannot assist with account issues on this site. See My Account is Compromised/Hacked and I Can't Log In! and How to Connect... |
| Document | Description |
|---|---|
| What kind of data can I get from the API? | To explore the kind of data available to you in the API, browse the available resources and this field guide to the most commonly accessed platform objects. |
| How can I keep up with changes to the Twitter API? | There are a two great ways to follow the changes we make to the Twitter platform: Follow @twitterapi. Keep track of our Developer Blog and Discussions. See the recently updated documentation. |