| Document | Description |
|---|---|
| The t.co URL Wrapper | Tens of millions of links are tweeted on Twitter each day. Wrapping these shared links helps Twitter protect users from malicious content while offering useful insights on engagement. All links submitted within tweets and direct messages, regardless of length, will eventually be wrapped with t.co... |
| GET direct_messages/show/:id | Returns a single direct message, specified by an id parameter. Like the /1/direct_messages.format request, this method will include the user objects of the sender and recipient. Important: This method requires an access token with RWD (read, write... |
| Streaming API | Introduction The Twitter Streaming API allows high-throughput near-realtime access to various subsets of public and protected Twitter data. Developers are strongly encouraged to read all of the documentation linked to by this document thoroughly. Products There are three main Streaming... |
| Document | Description |
|---|---|
| GET trends/:woeid | Returns the top 10 trending topics for a specific WOEID, if trending information is available for it. The response is an array of "trend" objects that encode the name of the trending topic, the query parameter that can be used to search for the topic on Twitter Search, and the Twitter Search URL.... |
| Document | Description |
|---|---|
| Site Streams | Currently in beta. Currently in beta. Overview Important Items Limitations API Overview Implementation Suggestions Connection Management Asynchronous Processing Apply for Access 04/19/2011 Overview Site Streams, a new feature on the... |
| Document | Description |
|---|---|
| How Twitter wraps URLs with t.co | Twitter uses twitter-text to parse status bodies and extract the entities, including URLs, that are returned with tweet responses. To understand the types of http and https-based URLs that our parser will extract and wrap with t.co, peruse the URL conformance tests. At this time, the general rule... |
| Document | Description |
|---|---|
| Twitter IDs, JSON and Snowflake | When consuming the API using JSON, it is important to always use the field id_str instead of id. This is due to the way Javascript and other languages that consume JSON evaluate large integers. If you come across a scenario where it doesn't appear that id and id_str match, it's due to your... |
| Document | Description |
|---|---|
| GET statuses/show/:id | Returns a single status, specified by the id parameter below. The status's author will be returned inline. |
| Document | Description |
|---|---|
| Tweet Button | By using the Tweet Button, you agree to the Developer Rules of the Road. Overview The Tweet Button is a small widget which allows users to easily share your website with their followers. This page is for developers and users who wish to build their own Tweet Buttons. If you are looking for a... |
| Tweet Button FAQ | Which browsers does the Tweet Button support? Does the Tweet Button support other languages? What are the dimensions of the Tweet Button and Share Box? What happens if twitter.com has an error or is over capacity? I want to use multiple Tweet Buttons on my page. Is there anything I should... |
| Open Source Examples | Open source projects are a great way to learn from other developers' experience with the Twitter API. There are plenty out there! By Project Host By Language/Platform By Project Host CodePlex GitHub Google Code SourceForge By Language/Platform Cocoa/... |
| Streaming API Methods | Methods are versioned to allow backwards compatibility. The current version level is 1. statuses/filter Returns public statuses that match one or more filter predicates. At least one predicate parameter, follow, locations, or track must be specified. Multiple parameters may be specified... |
| Document | Description |
|---|---|
| GET trends/daily | Returns the top 20 trending topics for each hour in a given day. |
| GET trends/weekly | Returns the top 30 trending topics for each day in a given week. |
| Tweet Entities | 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 and structured data. How can I use... |
| Document | Description |
|---|---|
| Web Intents | By using Web Intents, you agree to the Developer Rules of the Road. Make it easy to bring interactivity to Tweets that you display on the web. Web Intents provide popup-optimized flows for working with Tweets & Twitter Users: Tweet, Reply, Retweet, Favorite, and Follow. They make it... |
| Follow Button | By using the Follow Button, you agree to the Developer Rules of the Road. Overview The Follow Button is a small widget which allows users to easily follow a Twitter account from any webpage. The Follow Button uses the same implementation model as the Tweet Button, and its integration is just... |
| Web Intents Javascript Events | By using Web Intents Javascript Events, you agree to the Developer Rules of the Road. If you're integrating your site with Twitter using Web Intents, the Tweet Button and the Follow Button, and you want to detect the value you're getting from the integration, Web Intents Events provide the... |
| Document | Description |
|---|---|
| Developer Rules of the Road | Last Update - 1st of June 2011 Rules of the Road Twitter maintains an open platform that supports the millions of people around the world who are sharing and discovering what's happening now. We want to empower our ecosystem partners to build valuable businesses around the information flowing... |
| 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,... |