| Document | Description |
|---|---|
| GET statuses/oembed | Returns information allowing the creation of an embedded representation of a Tweet on third party sites. See the oEmbed specification for information about the response format. While this endpoint allows a bit of customization for the final appearance of the embedded Tweet, be aware that the... |
| Document | Description |
|---|---|
| Sign in with Twitter | Place a button on your site or application which allows Twitter users to enjoy the benefits of a registered user account in as little as one click. Works on websites, iOS, mobile and desktop applications. Features Ease of use - A new visitor to your site only has to click two buttons in... |
| Sign in with Twitter Resources | Client libraries The client libraries listed at Twitter Libraries will help implement Sign in with Twitter. Just make sure to use the /oauth/authenticate endpoint, as described in Implementing Sign in with Twitter. Buttons Twitter would prefer your application to use the following... |
| Document | Description |
|---|---|
| Single-user OAuth with Examples | Twitter offers the ability for you to retrieve a single access token (complete with oauth_token_secret) from application detail pages found on dev.twitter.com. This is ideal for applications migrating to OAuth with single-user use cases. You shouldn't ever share the combination of your OAuth... |
| Tokens from dev.twitter.com | Overview The dev.twitter.com application control panel offers the ability to generate an OAuth access token for the owner of the application. This is useful if: Your application only needs to make requests on behalf of a single user (for example, establishing a connection to the... |
| Document | Description |
|---|---|
| GET lists/subscriptions | Obtain a collection of the lists the specified user is subscribed to, 20 lists per page by default. Does not include the user's own lists. |
| Document | Description |
|---|---|
| GET followers/ids | Returns an array of numeric IDs for every user following the specified user. This method is powerful when used in conjunction with users/lookup. |
| GET lists | Returns the lists of the specified (or authenticated) user. Private lists will be included if the authenticated user is the same as the user whose lists are being returned. |
| Document | Description |
|---|---|
| Percent encoding parameters | This page covers the URL encoding process described in RFC 3986, Section 2.1. You should reference that specification in case of any ambiguity or conflict with this document. Overview Parts of the Twitter API, particularly those dealing with OAuth signatures, require strings to be... |
| Document | Description |
|---|---|
| Migrating tokens to system accounts | Overview It is very common for applications to have previously verified and stored a user’s access tokens, either through an existing iOS application or via a server-side integration. To leverage the power of the Twitter framework in iOS5, it is easy to migrate the user's access tokens to the... |
| Using the Tweet Sheet | Overview The Twitter framework includes a powerful all-in-one class for composing Tweets called TWTweetComposeViewController, also known as the "Tweet Sheet". The Tweet Sheet provides multiple mechanisms that enhance the user experience that have previously required developer support to implement... |
| Document | Description |
|---|---|
| PIN-based authorization | Overview The PIN-based OAuth flow is intended for applications which cannot access or embed a web browser in order to redirect the user to the authorization endpoint. Examples of such applications would be command-line applications, embedded systems, game consoles, and certain types of mobile... |
| GET lists/all | Returns all lists the authenticating or specified user subscribes to, including their own. The user is specified using the user_id or screen_name parameters. If no user is given, the authenticating user is used. |
| GET friendships/exists | Test for the existence of friendship between two users. Will return true if user_a follows user_b, otherwise will return false. Authentication is required if either user A or user B are protected. Additionally the authenticating user must be a follower of the protected user. Consider using... |
| POST lists/members/destroy | Removes the specified member from the list. The authenticated user must be the list's owner to remove members from the list. |
| GET lists/memberships | Returns the lists the specified user has been added to. If user_id or screen_name are not provided the memberships for the authenticating user are returned. |
| POST lists/subscribers/create | Subscribes the authenticated user to the specified list. |
| POST lists/subscribers/destroy | Unsubscribes the authenticated user from the specified list. |
| POST lists/destroy | Deletes the specified list. The authenticated user must own the list to be able to destroy it. |
| POST lists/update | Updates the specified list. The authenticated user must own the list to be able to update it. |