| Document | Description |
|---|---|
| Using OAuth | Introduction Understanding the way OAuth works can help create and debug applications which use Twitter's API. To use OAuth, an application must: Obtain access tokens to act on behalf of a user account. Authorize all HTTP requests it sends to Twitter's APIs. The following... |
| Document | Description |
|---|---|
| POST direct_messages/new | Sends a new direct message to the specified user from the authenticating user. Requires both the user and text parameters and must be a POST. Returns the sent message in the requested format if successful. |
| POST account/update_profile_banner | Uploads a profile banner on behalf of the authenticating user. For best results, upload an |
| POST account/remove_profile_banner | Removes the uploaded profile banner for the authenticating user. Returns HTTP 200 upon success. |
| Document | Description |
|---|---|
| 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... |
| 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... |
| 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... |
| Document | Description |
|---|---|
| Useful Links We Found | On using API v1.1 Using API v1.1 with the SignPost library for Scala or Java Streaming data from Twitter using the 1.1 Search API On OAuth Apigee's OAuth: the Big Picture Using OAuth for Twitter Authentication on the BlackBerry PlayBook Using Twitter API with LIFT, Scala, and... |
| Document | Description |
|---|---|
| xAuth | About xAuth xAuth is still OAuth. You still need to master how to send signed requests to Twitter. The xAuth process will only yield read-only or read-write access tokens. Direct message read access is not provided with xAuth. If your application requires access to a user's direct messages,... |
| Document | Description |
|---|---|
| Image Resources | The resources are available to support a consistent user experience in applications leveraging Twitter & sites using Web Intents. It is recommended that you store these within your own application. For more information on using these marks, consult our Display Requirements. Birds... |
| Document | Description |
|---|---|
| What is the version of the REST API? | There are currently two active versions of the Twitter REST API. REST API version 1.1 is the most recent version of the API. To unifying versioning across the platform, version 1.1 also encompasses the Search and Streaming APIs. REST API version 1 is now deprecated and will cease functioning in... |
| Document | Description |
|---|---|
| GET lists/members | Returns the members of the specified list. Private list members will only be shown if the authenticated user owns the specified list. |
| Document | Description |
|---|---|
| GET statuses/retweets/:id | Returns up to 100 of the first retweets of a given tweet. |
| @Anywhere Features: Tweet Box | @Anywhere is deprecated and will cease functioning soon. See Sunsetting @Anywhere for more information. Overview The Tweet Box allows Twitter users to tweet directly from within your web site or web application. Basic Usage The default Tweet Box will work without any customizations and... |
| Welcome to @Anywhere | @Anywhere is deprecated and will cease functioning soon. See Sunsetting @Anywhere for more information. Twitter @Anywhere is an easy-to-deploy solution for bringing the Twitter communication platform to your site. @Anywhere promotes a more engaged user base for your site. Use @Anywhere to... |
| Document | Description |
|---|---|
| GET users/show | Returns a variety of information about the user specified by the required user_id or screen_name parameter. The author's most recent Tweet will be returned inline when possible. GET users/lookup is used to retrieve a bulk collection of user objects. |
| POST account/update_profile_image | Updates the authenticating user's profile image. Note that this method expects raw multipart data, not a URL to an image. This method asynchronously processes the uploaded file before updating the user's profile image URL. You can either update your local cache the next time you request the user's... |
| GET lists/statuses | Returns tweet timeline for members of the specified list. Retweets are included by default. You can use the include_rts=false parameter to omit retweet objects. Embedded Timelines is a great way to embed list timelines on your website. |
| Document | Description |
|---|---|
| POST direct_messages/destroy | Destroys the direct message specified in the required ID parameter. The authenticating user must be the recipient of the specified direct message. Important: This method requires an access token with RWD (read, write... |
| Working with Timelines | Introduction The Twitter API has several methods, such as GET statuses/user_timeline, GET statuses/home_timeline and GET search/tweets, which return a timeline of Tweet data. Such timelines can grow very large, so there are limits to how much of a timeline a client application may fetch in a... |