| Document | Description |
|---|---|
| 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... |
| Document | Description |
|---|---|
| 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. |
| User Profile Images and Banners | Profile Images Profile images (or avatars) are an important component of a Twitter account's expression of identity. To upload an avatar on behalf of a user, use POST account/update_profile_image. Alternative image sizes for user profile images You can obtain a user's most recent profile image,... |
| GET users/profile_banner | Returns a map of the available size variations of the specified user's profile banner. If the user has not uploaded a profile banner, a HTTP 404 will be served instead. This method can be used instead of string manipulation on the profile_banner_url returned in user objects as described in User... |
| 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 |
|---|---|
| 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... |
| Document | Description |
|---|---|
| How do I get access tokens from my iOS native Twitter application to my server? | Using Reverse Auth is a method of converting the access representations available in the Integrating with Twitter on iOS. |
| Adding the Social framework | Overview The Social Framework in iOS6 makes it easy for you to leverage the power of Twitter for single sign-on, content personalization and content sharing. This document walks you through the simple process of adding the framework to a new or existing project. Apple's Documentation For... |
| Migrating tokens to system accounts | Overview It is very common for applications to have previously verified and stored Twitter users' access tokens, either through an existing iOS application or via a server-side integration. Thankfully, it is easy to migrate these access tokens to the device so that you can... |
| Integrating with Twitter on iOS | Overview Go to the source What can I do with the framework? Single Sign-On Distribution Instant Personalization Accessing the Twitter API Have questions? Overview Apple includes a framework that enables your iOS applications to leverage the power of Twitter. This framework removes... |
| Using the Tweet Sheet | Overview The Social framework includes a powerful all-in-one class for composing Tweets called SLComposeViewController, 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 |
|---|---|
| Tweets | Also known as a Status Update, Tweets are the basic atomic unit of all things Twitter. Users create Tweets. Tweets can be embedded, replied to, favorited, unfavorited, retweeted, unretweeted and deleted. A retweet contains an embedded Tweet object within the "retweeted_status" attribute.... |
| Streaming message types | Public stream messages Blank lines Status deletion notices (delete) Location deletion notices (scrub_geo) Limit notices (limit) Withheld content notices (status_withheld, user_withheld) Disconnect messages (disconnect) User stream messages Friends lists (friends) Events (event... |
| Embedded Timelines Most Frequent Problems (and their solution) | Get the latest version First, make sure you got the new embedded timeline (widget) code from https://twitter.com/settings/widgets/new. The widget does not work, it just shows "tweets by @username" on my page. This is most likely a problem with your widget domain configuration. By going in your... |
| Document | Description |
|---|---|
| Embedded Timelines | Overview Embeddable timelines make it easy to syndicate any public Twitter timeline to your website with one line of code. Just like timelines on twitter.com, embeddable timelines are interactive and enable your visitors to reply, Retweet, and favorite Tweets directly from your pages. Users... |
| Document | Description |
|---|---|
| GET statuses/retweets_of_me | Returns the most recent tweets authored by the authenticating user that have recently been retweeted by others. This timeline is a subset of the user's GET statuses/user_timeline. See Working with Timelines for instructions on traversing timelines. |
| Document | Description |
|---|---|
| REST API Rate Limiting in v1.1 | Per User Rate limits in version 1.1 of the API are considered on a per-user basis — or more accurately described, per access token in your control. If a method allows for 15 requests per rate limit window, then it allows you to make 15 requests per window per leveraged access token. This is... |
| Document | Description |
|---|---|
| GET statuses/mentions_timeline | Returns the 20 most recent mentions (tweets containing a users's @screen_name) for the authenticating user. The timeline returned is the equivalent of the one seen when you view your mentions on twitter.com. This method can only return up to 800 tweets. See Working with Timelines for... |
| Document | Description |
|---|---|
| Why am I getting a HTTP 404 for my timeline feed? | If you're requesting a timeline URL that used to work but now does not, you are likely using an outdated URL that has been retired. In March of 2012 we announced that "unversioned endpoints," GET statuses/public_timeline, and the v1 REST ATOM response format were deprecated and would eventually... |