Document | Description |
---|---|
How do I identify and work with retweets? | In v1.1 APIs, retweeted tweets are expressed through nested objects. If you encounter a tweet object that contains a retweeted_status node, the tweet represents a retweet. The embedded retweeted_status is the tweet that has been retweeted and the outer object represents the retweet event itself.... |
Document | Description |
---|---|
Embedded Tweets | Overview Embedded Tweets make it possible for you take any Tweet and embed it directly in to the content of your article or website. Tweets display with expanded media like photos, videos, and article summaries, and also include real-time retweet and favorite counts. When embedded, Tweets are... |
Streaming API request parameters | Use the following request parameters to define what data is returned by the Streaming API endpoints: delimited stall_warnings filter_level language follow track locations count with replies stringify_friend_ids delimited This parameter may be used on all streaming... |
POST statuses/update_with_media | Updates the authenticating user's current status and attaches media for upload. In other words, it creates a Tweet with a picture attached. Unlike POST statuses/update, this method expects raw multipart data. Your POST request's Content-Type should be set to multipart/form-data with the media[]... |
Player Card | This Card type requires special approval, and is not available for immediate approval at this time. The Player Card is for streaming media experiences such as audio, video, or slideshows, and allows you to present your content inside of an iframe within the Tweet. Unlike the photo and... |
Tweet Entities | See also Entities from the Field Guide. Why Tweet Entities? Tweet text can potentially mention other users or lists, but also contain URLs, media, hashtags... Instead of parsing the text yourself to try to extract those entities, you can use the entities attribute that contains this parsed... |
Error Codes & Responses | HTTP Status Codes The Twitter API attempts to return appropriate HTTP status codes for every request. It is possible to suppress response codes for the REST API. Code Text Description 200 OK Success... |
Document | Description |
---|---|
Player Card Whitelisting | Thank you for your interest in using the Twitter Player Card. To help expedite the whitelisting of your Card, it is useful to read the below fully and provide the appropriate information. Unfortunately, we are currently backlogged in our approval of Player Cards, so responses may vary... |
Document | Description |
---|---|
Troubleshooting Twitter Cards | We created this troubleshooting guide to help you identify and resolve commonly encountered issues during Cards development. Please look over the below categories to see which most resembles your issue. Card Validator Card Whitelisting Cards on the Timeline Debugging Player Cards Mixed Content/... |
Getting Started | Getting Started with Cards Card and Content Attribution URL Crawling Twitter Cards and Open Graph Getting Started with Cards To get started with implementing the Cards markup, you'll want to specify the type of card for your content by adding the following HTML to the HEAD section... |
Calendar of API changes | This page lists important upcoming dates for consumers of Twitter's APIs. The dates listed will be as specific as possible, but may not be exact for various reasons. Please continue to follow @twitterapi and the Twitter developer blog for announcements about the platform. Upcoming changes... |
Document | Description |
---|---|
Connecting to Twitter API using SSL | The preferred method of connecting to the Twitter API is over HTTPS. While both HTTPS and Non-HTTPS connections to the Twitter API are supported, communicating over SSL preserves user privacy by protecting information between the user and the Twitter API as it travels across the public Internet... |
Document | Description |
---|---|
Integrating with Twitter on iOS | The official iOS SDK includes a framework that enables your iOS applications to leverage the power of Twitter. This framework removes many of the common obstacles encountered when accessing Twitter's API, including authentication and Tweet composition, and allows developers to focus on more... |
Document | Description |
---|---|
Using Reverse Auth | While the Twitter framework for iOS provides an incredibly easy way to make authenticated calls on behalf of a user to the Twitter API, you may find the need to process a user’s Twitter data on your server. To faciliate this, Twitter provides an endpoint that allows you to obtain the user's OAuth... |
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 |
---|---|
Using the Tweet Sheet | Overview The Tweet Sheet 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 previously required developer... |
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 take advantage of the... |
API requests with SLRequest | Overview SLRequest is a class in the Social.framework for iOS that encapsulates HTTP requests to Twitter’s REST API. This class supercedes the Twitter.framework's TWRequest from iOS5. How do I perform requests with SLRequest ? Executing a request to Twitter's REST API is a 3 step process: First... |
Frequently Asked Questions | Why do I receive authentication errors when using SLRequest? Are Social.framework status updates' URLs automatically wrapped in t.co? Why is my application attributed as "from iOS" instead of "from <my application>" on twitter.com? I'm seeing strange crashes when... |
Document | Description |
---|---|
Application-only authentication | Overview Twitter offers applications the ability to issue authenticated requests on behalf of the application itself (as opposed to on behalf of a specific user). Twitter's implementation is based on the Client Credentials Grant flow of the OAuth 2 specification. Note that OAuth 1.0a is still... |