The WHO, WHAT, WHERE, WHEN, WHY, HOW* of Building APIs…

(* not in that order)

Javaun Moradi, NPR@javaun

(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

(Last background slide for a while)

NPR’s APIs• Stories• Stations• Schedules• Streams• Library data• Transcripts• …

WHY are APIs so sexy?

APIs are about the opportunities you don’t miss.

WHY do we love APIs?

• Keep pace with your product needs• Innovate quickly• Reuse, don’t reinvent• Serendipity

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)?

WHAT do you build?

Smart small(you can add more later)

Build for actual user problems(Don’t “liberate” data unless that’s your mission)

Intuitive and self-documenting(developers hate to read)

Drink your own… (be your first customer)

Build something imperfect. (Be ok with that.)

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?

WHO do you want to be? (Big IT vs. Leading the business)

WHO do you build it for?

WHERE should your API live?

public private

One size

Custom

• Data.gov• Sunlight Labs

• Netflix

• World Bank

• NPR API we use

• Google

• Twilio

• Open NPR API

• AP

HOW: DIY vs. Vendor

HOW do you support it?

Now what?(Hang on tight…)