The document discusses key aspects of building APIs including why organizations build APIs, when it is time to develop an API, what types of APIs should be built, who APIs should be built for, and how APIs should be supported. Specifically, it notes that NPR launched its open API in 2008 which powers NPR's mobile, web, and car applications and allows over 100 stations to access and customize content. It also provides examples of the types of data that NPR's APIs expose like stories, stations, schedules, streams, and transcripts.
Building APIs: The WHO, WHAT, WHERE, WHEN, WHY and HOW
1. The
WHO, WHAT, WHERE, WHEN, WHY,
HOW* of Building APIs…
(* not in that order)
Javaun Moradi, NPR
@javaun
2. (This slide isn’t a “W” or “H”)
• NPR Open API launched in 2008
• Try it: http://dev.npr.org or Codecademy.com
• Powers all of NPR’s mobile, web, cars apps
• 100+ stations retrieve content & add their
own
3. (Last background slide for a while)
NPR’s APIs
• Stories
• Stations
• Schedules
• Streams
• Library data
• Transcripts
• …
6. WHY do we love APIs?
• Keep pace with your product needs
• Innovate quickly
• Reuse, don’t reinvent
• Serendipity
7. WHEN is it time to get an API?
• Mobile aspirations?
• Data/services useful in more than one place?
• Departments need to share/collaborate?
• Decouple your systems?
• Be more nimble?
• Share your service (free or for profit)?
14. WHAT should you measure?
• Speed, for starters
• Usage is great for management
• Do you monetize your API?
• Numbers don’t tell you value
• Do you measure other tools?
15. WHO do you want to be?
(Big IT vs. Leading the business)
18. WHERE should your API live?
• Data.gov One size
• Sunlight Labs • AP
• World Bank
• Open NPR API • NPR API we use
public private
• Twilio
• Google
Custom • Netflix
The reality is that NPR, stations, and partners were almost all of the usage.
This is not an authoritative depiction of where these APIs live, it’s an exercise I used to think about where our APIs should live and how much resources/time should go into each area.
The space is really nascent. We don’t know where it’s going to go. It is critical to our business and we want to be in full control of our roadmap. It’s our core technology, we’re invested.