|
GET help/tos |
Returns the Twitter Terms of Service in the requested format. These are not the same as the Developer Rules of the Road. |
|
GET help/privacy |
Returns Twitter's Privacy Policy. |
|
GET help/languages |
Returns the list of languages supported by Twitter along with their ISO 639-1 code. The ISO 639-1 code is the two letter value to use if you include lang with any of your requests. |
|
GET help/configuration |
Returns the current configuration used by Twitter including twitter.com slugs which are not usernames, maximum photo resolutions, and t.co URL lengths.
It is recommended applications request this endpoint when they are loaded, but no more than once a day. |
|
GET geo/similar_places |
Locates places near the given coordinates which are similar in name.
Conceptually you would use this method to get a list of known places to choose from first. Then, if the desired place doesn't exist, make a request to POST geo/place to create a new one.
The token contained in the response is the... |
|
GET geo/reverse_geocode |
Given a latitude and a longitude, searches for up to 20 places that can be used as a place_id when updating a status.
This request is an informative call and will deliver generalized results about geography. |
|
GET geo/search |
Search for places that can be attached to a statuses/update. Given a latitude and a longitude pair, an IP address, or a name, this request will return a list of all the valid places that can be used as the place_id when updating a status.
Conceptually, a query can be made from the user's location... |
|
GET geo/id/:place_id |
Returns all the information about a known place. |
|
GET friendships/lookup |
Returns the relationships of the authenticating user to the comma-separated list of up to 100 screen_names or user_ids provided. Values for connections can be: following, following_requested, followed_by, none. |
|
GET friendships/incoming |
Returns a collection of numeric IDs for every user who has a pending request to follow the authenticating user. |
|
GET friends/ids |
Returns a cursored collection of user IDs for every user the specified user is following (otherwise known as their "friends").
At this time, results are ordered with the most recent following first — however, this ordering is subject to unannounced change and eventual consistency issues.... |
|
GET friendships/outgoing |
Returns a collection of numeric IDs for every protected user for whom the authenticating user has a pending follow request. |
|
GET friendships/show |
Returns detailed information about the relationship between two arbitrary users. |
|
GET direct_messages/sent |
Returns the 20 most recent direct messages sent by the authenticating user. Includes detailed information about the sender and recipient user. You can request up to 200 direct messages per call, up to a maximum of 800 outgoing DMs.
Important: This method requires an access token with RWD (read,... |
|
GET direct_messages/show |
Returns a single direct message, specified by an id parameter. Like the /1.1/direct_messages.format request, this method will include the user objects of the sender and recipient.
Important: This method requires an access token with RWD (read, write... |
|
GET account/verify_credentials |
Returns an HTTP 200 OK response code and a representation of the requesting user if authentication was successful; returns a 401 status code and an error message if not. Use this method to test if supplied user credentials are valid. |
|
GET account/settings |
Returns settings (including current trend, geo and sleep time information) for the authenticating user. |
|
Follow Button |
The Follow Button is a small widget which allows users to easily follow a Twitter account from any webpage. The Follow Button uses the same implementation model as the Tweet Button, and its integration is just as simple.
By using the Follow Button, you agree to the Developer Rules of the Road.... |
|
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... |
|
API Terms of Service: Archive |
Previous API Terms of Service (NOT CURRENT)
Please Note: These terms are NOT current. Please read the current terms.
Most recent changes
May 5, 2012
June 1, 2011
April 13, 2011
|