API-Craft NYC - Overview of the Twitter APIs with demos
2 likes402 views
The document outlines key information on Twitter's APIs, including their importance, organization, rate limits, and versioning. It provides an overview of different types of APIs such as streaming and REST, along with their functionalities and limitations. Additionally, it highlights resources for developers, including documentation and code examples.
API-Craft NYC - Overview of the Twitter APIs with demos
- 1. Jon Bulava @jbulava Editor-in-chief, Developer Relations @Twitter. Master of web technology. Top it off with some photography and video production. Follow
- 2. - Why is Twitter important? - API overview - Organization - Rate limits - Versioning - Demos - Open discussion AGENDA
- 3. - Connect your users with their interests - Distribution on a global scale - Open and real-time WHY IS TWITTER IMPORTANT?
- 4. Streaming APIsREST APIs API OVERVIEW Ingest what’s happening right now Perform actions Access what happened
- 5. Public API Media API Collections API TON API API ORGANIZATION Streaming APIsREST APIs User streams Site streams Public streams
- 6. API ORGANIZATION Streaming APIsREST APIs POST statuses / filter GET statuses / sample GET statuses / firehose User streams Site streams Public streams GET site GET user Public API GET statuses/user_timeline GET statuses/show/:id POST statuses/update GET search/tweets GET followers/list GET trends/place Media API POST media/upload POST media/upload (INIT) POST media/upload (APPEND) POST media/upload (FINALIZE) POST media/metadata/create GET media/upload (STATUS)
- 7. API RATE LIMITS Streaming APIsREST APIs Reasons for limiting: • Backoff strategy not implemented • Frequent breaks and reconnecting • Too many connections Limit notices { "limit":{ "track":1234 } } 15 minute windows Most limits are either: • 15 calls / 15 minutes • 180 calls / 15 minutes
- 8. Streaming APIsREST APIs Ads APIs API VERSIONING
- 9. Ads APIs API VERSIONING • Frequent updates means aggressive versioning • MAJOR and MINOR numbers used (e.g. 2.3) • Backward incompatible increases MAJOR • Backward compatible increases MINOR • Only need to specify MAJOR number in call Example: https://ads-api.twitter.com/1/accounts/abc1/tailored_audiences
- 10. DEMO
- 11. Documentation dev.twitter.com Streaming API t.co/streaming REST API t.co/rest DEVELOPER RESOURCES Create App t.co/apps Open Source Libs t.co/libs Code Examples t.co/code