Your SlideShare is downloading. ×
Finishing your 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

Finishing your API

1,492
views

Published on

Going from a read API to a write API at Etsy

Going from a read API to a write API at Etsy

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,492
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
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
  • A little about Etsy My background – YDN The story (Craftcult) Our experience developing our API with Mashery (reference Yahoo! experience) Uptake, lessons Looking ahead – what does it mean to “finish” your API?
  • We also noticed that there were unofficial libraries to use this API
  • I joined Etsy in September 2008 from Yahoo, where I ran YDN Noticed api.etsy.com in Flash Other apps like craftcult Ruby gem to reverse engineer our API Hacker mailing list – the “Etsy Underground” “ When you’re being scraped, time to release an API”
  • Transcript

    • 1. Finishing your API Chad Dickerson, CTO Etsy, http://www.etsy.com/ Business of APIs Conference November 16, 2009
    • 2. What is Etsy?
    • 3. Etsy is social, both on Etsy. . . . . http://www.etsy.com/virtual_labs.php
    • 4. . . . and off Etsy http://www.twitter.com/etsy
    • 5. Etsy numbers (as of November 15, 2009)
      • 3.4 million registered members (over 250,000 sellers)
      • 4.8 million active items in the marketplace
      • 640 million page views in last 30 days
      • $17.7 million in goods sold in October ’09
      • Over 1 million items sold in October ‘09
      • Over 1,075,000 Twitter followers for @Etsy
      • Over 1 million forum posts per month on Etsy.com
    • 6. Why an API?
      • So…..why an API for Etsy?
    • 7. The “unofficial” API http://www.etsy.com/color.php
    • 8. . . . plus eager developers
    • 9. Craftcult http://www.craftcult.com/
    • 10. The ecosystem was already forming
      • The “Etsy Underground”
      • Real 3 rd party apps on the platform that our users liked and were good for everyone
      • 3 rd party code libraries available
      • Defined set of services with built-in community
      • When you’re being scraped, it’s a clear sign that you need to release an API
    • 11. Getting the API up quickly: partnering with Mashery http://developer.etsy.com/
    • 12. Results from v1 of our API
      • Today
      • Over 9 million API calls per month, 100+ active devs
      • 17 featured applications, including 5 Etsy-themed iPhone apps: http://developer.etsy.com/applications
      • Craftcult continues to a substantial traffic driver
      • Simple BD deals enabled
      • 2 developers hired!
    • 13. Solid start. . . .
      • This is a solid start, but to truly realize our investment, we need to do more. . . .
    • 14. Finishing your API
      • Deliver read/write API . The web is bi-directional. The best apps put data into the system, too.
      • Access to private data . The most interesting apps will be personalized for our members.
      • More ways for developers to make money . The richer the API, the more opportunities.
      • Make Etsy even more social with the API . Recognize unique strengths and build upon them with our API.
    • 15. Final notes
      • A good API is never finished
      • It is organic and continues to grow as your business grows.
      • If you think your API is ever “done,” you’re thinking too short-term
    • 16. Questions?
      • Questions?