Your SlideShare is downloading. ×
0
The Rebirth of Twitter's API
The Rebirth of Twitter's API
The Rebirth of Twitter's API
The Rebirth of Twitter's API
The Rebirth of Twitter's API
The Rebirth of Twitter's API
The Rebirth of Twitter's API
The Rebirth of Twitter's API
The Rebirth of Twitter's API
The Rebirth of Twitter's API
The Rebirth of Twitter's API
The Rebirth of Twitter's API
The Rebirth of Twitter's API
The Rebirth of Twitter's API
The Rebirth of Twitter's API
The Rebirth of Twitter's API
The Rebirth of Twitter's API
The Rebirth of Twitter's API
The Rebirth of Twitter's API
The Rebirth of Twitter's API
The Rebirth of Twitter's API
The Rebirth of Twitter's API
The Rebirth of Twitter's API
The Rebirth of Twitter's API
The Rebirth of Twitter's API
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

The Rebirth of Twitter's API

3,241

Published on

This presentation takes a look back at some other popular APIs that have met their demise, gives an understanding of what's new with Twitter's API v1.1, and provides information on how to protect …

This presentation takes a look back at some other popular APIs that have met their demise, gives an understanding of what's new with Twitter's API v1.1, and provides information on how to protect yourself (and your app) from being negatively impacted by these kinds of changes in the future.

http://blog.smartbear.com/api-monitoring/the-rebirth-of-twitters-api/

Published in: Technology
0 Comments
11 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
3,241
On Slideshare
0
From Embeds
0
Number of Embeds
12
Actions
Shares
0
Downloads
0
Comments
0
Likes
11
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. The Rebirth ofTwitter’s API
  • 2. Twitter’s API v1.0was put to rest tomake room for v2.0.But wait……
  • 3. Why is Twitterretiring its APIv1.0?
  • 4. Previously, Twitter’s API could be accessedwithout authorization, so malicious sites andapplications had easy access.This, of course, presenteda security risk.
  • 5. So, security risks and adesire for uniformity acrossall third-party applicationsnecessitated a switch to v1.1.
  • 6. …But why 1.1instead of 2.0?
  • 7. Twitter is not switching to API v2.0 butinstead switching to the v1.1 it originallyintroduced in Fall 2012.This allows for an adjustment periodbefore they abandon v1.0 entirely.As it turnsout…
  • 8. Were extending the API v1.0 retirementdate from May 7, 2013 to June 11, 2013in order to accommodate additionalblackout testing.-- TwitterSource: https://dev.twitter.com/blog/api-v1-retirement-date-extended-to-june-11
  • 9. How v1.1 isdifferent?
  • 10. Version 1.1 of the API will require allapplications to authenticate everyrequest. For applications that alreadyuse OAuth, those tokens will transitionover to the new version.- Zach Walton of WebProNewsSource: http://www.webpronews.com/twitter-api-version-1-1-brings-more-regulation-to-apps-2012-08
  • 11. In order to improve the security evenfurther, when third-party appsrefresh they’ll run up againstTwitters rate limit.----------------“The rate was 350 times per hour.However, after the change tookplace this rate limit was changed to60 times per hour for each task and720 times per hour for popular datasuch as tweets.”Source: http://quotient.net/blog/2012/9/21/twitters-recent-api-changes-and-how-it-affects-your-business/
  • 12. Twitter API is going to strictlysupport JSON only.“Weve decided to discontinuesupport for XML, Atom, andRSS, which are infrequently usedtoday.”How else is v1.1 different?Source: https://dev.twitter.com/docs/api/1.1/overview
  • 13. Why all the controversy?----------------A big controversy erupted overthe 100,000 user limit now inplace. Before the latest change totheir API, Twitter clients had nolimit.
  • 14. The one million user limit means that if you sign up toTwitter clients you can never have more than 100,000 usersever (well, unless Twitter gives you specialpermission, which is a rarity).Third-party Twitter apps that currently have millions of userswill definitely be affected, unless they are given specialpermission to expand their user limit. Some third-party appssuch as Tweetcaster would have a cap at 200 percent ordouble their user base, which would seriously affect theirgrowth.- John CurtisSource: http://quotient.net/blog/2012/9/21/twitters-recent-api-changes-and-how-it-affects-your-business/
  • 15. The greatest change fuelingcontroversy and complaint isthe new “Developer Rules ofthe Road” that originallybegan as a guideline fordisplay in third-partyapplications.
  • 16. These guidelines have now becomerequirements designed to “foster aconsistent Twitter experience.”------------Those will include scaling tweetsappropriately based on the deviceon which the application is used;displaying Tweet actions such asreply, retweet and favorite; andlinking @usernames to theappropriate profile.Source: https://dev.twitter.com/terms/api-terms
  • 17. The demise of otherwell-known APIs
  • 18. Google--------------Without announcement, Google gotrid of their weather API.“As this is a private API, Google isarguably entitled to pull supportwithout warning but that won’t stopdevelopers being disappointed by themove and lack of communication.”Source: http://thenextweb.com/google/2012/08/28/did-google-just-quietly-kill-private-weather-api/
  • 19. Path-------------Following a spam controversy inPath, a popular mobileapp, Facebook has restricted Path’sAPI access so that you can nolonger look up Facebook friends onthe app.Losing this ability could hinder thegrowth of this application, now at 10million registered users.Source: http://techcrunch.com/2013/05/04/path-blocked/
  • 20. Facebook-----------Like Path, Facebook alsoblocked this “find friend”feature from apps likeVoxer, Wonder, and Vine.There is speculation thatFacebook is trying to stopcompetition that they deem“similar” to their own availableservices.Source: http://allfacebook.com/facebook-platform-policy-voxer-wonder-vine_b109372
  • 21. Testing & MonitoringThird-Party APIs
  • 22. When it comes to third-partyAPIs, it’s important to be safe.Research: Know your choices, check reviewsDefend: Define your thresholds, response timesTest: Make sure it worksMonitor: Be first to report, ensure performance
  • 23. Know how to test your third-party APIs effectively, soyou don’t end up sufferingthe consequences.---------- Include APIs in test plansas if it was your own code Add APIs to regressiontests
  • 24. Know what’s going on with third party APIsto make sure you’re not blindsided whenchange occurs. This helps prevent smallproblems from turning into bigproblems. That, in turn, keeps your websiteperforming optimally and your customersclicking contentedly.Effectively testing your third party APIs fordependability is key to getting, andkeeping, high customer satisfaction.
  • 25. Are you trying to monitor theperformance of your third party API?AlertSite for API Monitoring helps some of the world’sbest-known companies keep their APIs and websites upand running.http://bit.ly/AlertSite-API-Monitoring

×