Peter Orlowsky provides insights into the strategy choices that created Getty Images’ API program and the customer/business value the API creates.
Giovanni Asproni expands upon the idea that usable APIs help writing clean code.
Irakli Nadareishvili, Jon Moore, and Anthony Cuellar share insight in creating teams and building media APIs for distributing content.
Andrew Mager, Paul Osman, Evan Stein and R. Kevin Nelson share from their experience introducing a music API culture into their companies and developing such APIs.
Rickard Oberg explains how to expose use-cases to solve the linking problem in RESTful APIs, and how this will simplify both API development, documentation, as well as client development.
Mike Amundsen describes the ALPS standard, a way to define the data and workflow details for a Web application and apply these details consistently regardless of the media type in use.
Gray Brooks discusses the efforts around creating APIs for accessing the vast amounts of data administered by the US Government.
Paul Downey and David Heath discuss the UK Government Digital Service API Design Principles, the lessons learnt from building the GOV.UK publishing platform and transactional services on APIs.
Ben Christensen describes how Neflix has optimized their API using a functional reactive programming (modeled after Rx) in a polyglot Java stack.
Daniel Jacobson shares advice on dealing with evolving APIs based on his experience with Netflix APIs.
Jeff Meisel shares insight in National Instruments’ attempt to create an open API for their software spanning 25 years.