|
POST geo/place |
Creates a new place object at the given latitude and longitude.
Before creating a place you need to query GET geo/similar_places with the latitude, longitude and name of the place you wish to create. The query will return an array of places which are similar to the one you wish to create, and a... |
|
I'm a teapot, how does API v1.1 affect me? |
418. #nuffsaid |
|
I'm a user, how does API v1.1 affect me? |
There should not be any major impact for users. |
|
I'm not a developer, how do I render tweets according to display requirements? |
You can review our Developer Display Requirements. Embedded Tweets and Embedded Timelines are easy ways to implement display requirements. |
|
POST account/update_delivery_device |
Sets which device Twitter delivers updates to for the authenticating user. Sending none as the device parameter will disable SMS updates. |
|
In API v1.1 will developers be allowed include additional actions on Tweets such as "Send to Instagram," "Send Email," "Tweet of the Day?" |
No. Please leave the integrity of the Tweet intact. If you feel compelled to add additional content, please do so around or adjacent to the Tweet, but not within the actual Tweet itself. If you’re concerned about staying inline with our Developer Display Requirements, please see our Embedded... |
|
OAuth |
Send secure authorized requests to the Twitter API
Twitter uses OAuth to provide authorized access to its API.
Features
Secure - Users are not required to share their passwords with 3rd party applications, increasing account security.
Standard - A wealth of client libraries and... |
|
Control Streams for Site Streams |
Control Streams provides a REST-based interface that allows a developer to query and modify the state of a specific Site Streams connection. Use the same three-legged OAuth patterns you use to connect to Site Streams, where the access token used belongs to the user that owns the application that... |
|
GET site |
Streams messages for a set of users, as described in Site streams.
|
|
POST lists/subscribers/destroy |
Unsubscribes the authenticated user from the specified list. |
|
Rules of the Road Summary |
This a brief summary highlighting the themes of our Developer Rules of the Road. This is just a highlight brief, and is not intended to be a substitute for reading the terms of service in its entirety. A developer is still responsible for understanding and abiding by the Rules of the Road, but we’... |
|
POST friendships/destroy |
Allows the authenticating user to unfollow the user specified in the ID parameter.
Returns the unfollowed user in the requested format when successful. Returns a string describing the failure condition when unsuccessful.
Actions taken in this method are asynchronous and changes will be eventually... |
|
GET users/suggestions |
Access to Twitter's suggested user list. This returns the list of suggested user categories. The category can be used in GET users/suggestions/:slug to get the users in that category. |
|
POST account/update_profile_colors |
Sets one or more hex values that control the color scheme of the authenticating user's profile page on twitter.com. Each parameter's value must be a valid hexidecimal value, and may be either three or six characters (ex: #fff or #ffffff). |
|
POST lists/members/destroy_all |
Removes multiple members from a list, by specifying a comma-separated list of member ids or screen names. The authenticated user must own the list to be able to remove members from it. Note that lists can't have more than 500 members, and you are limited to removing up to 100 members to a list at a... |
|
GET user |
Streams messages for a single user, as described in User streams.
|
|
Overview: Version 1.1 of the Twitter API |
Version 1.1 of the Twitter API is the first major update of the API since its launch. We're excited about what it means for developers and we've captured all the meaningful changes here so you don't miss a thing.
Improved rate limits
JSON support only
Authentication required on all... |