This document discusses APIs and their future as open platforms. It covers how APIs provide a blank canvas for developers to build on, serving as fundamental building blocks. The document also examines what defines an open API, providing examples of signs of openness like being acknowledged, documented, and supported. Business models for APIs are presented, along with examples of organizations that have benefited from opening their APIs. The future of connected devices through open APIs is briefly touched on as well.

1. How Open
is Your API Future?
Adam DuVander – @adamd
Developer Communications Director,

2. APIs Provide a Blank Canvas
Flickr user sookie

3. APIs Are Building Blocks
Josh Wedin

4. Artists and Architects
N StjernaJeremy King

5. The Age of Scribes

6. Printing Press
Paul Anderson

15. Felipe Venâncio

16. Ray Devlin

20. 33 Dead Google APIs
programmableweb.com

22. Should
I have
an
API?

24. Should I
open
my
API?

26. Dec 2010
Jan 2011
Feb2011

27. Jul 2011
Sep2011
Jul 2012

29. What is open?
Free Anyone
Not Closed

30. Antti T. Nissinen

31. Signs of Open APIs
Acknowledged
Documented
Supported
Three Cs: bit.ly/the3Cs

32. How Twilio Got Intuit
Flickr user jo-h
“Mary”

33. Mary Reads, Signs Up

34. Payroll Verification
Flickr user sco
Big API Partner
no additional
work

36. Basic Business Models

37. John Musser, ProgrammableWeb
bit.ly/apibizmodels

39. US Fish and Wildlife
Bullish

41. “We find that if our customers use
any single integration, they are
three times as likely to convert to
paid.”

42. Connected Things

44. Heather Cowper

45. Flickr user jelm6
Thank You.
Let’s Chat:
@adamd
adam@sendgrid.com