This page is all about APIs, and the people/companies who work with them, the tools/languages the use, and of course the APIs themselves. Think of this as a cornucopia of API loveliness. Get your knapkin on!
I’m doing a little project that uses this information, check it out: Team API Development.
Who are the shovers and makers in the world of APIs?
- Adam DuVander is an API dude, editor at Programmable Web
- John Musser, who I saw do a great presentation at Gluecon, is founder of Programmable Web.
- Roy Fielding isn’t an API dude, he’s a REST dude. If you say your API is RESTful and it isn’t, he’ll smite you.
- Christian Reilly is an API believer, working at a large organization spreading the API marmite.
- Matthew Yeager has got “Chief” in his title, so he’s got to know what he’s talking about when it comes to APIs.
- Apigee are a company who only deal in APIs.
- Brian Mulloy works for Apigee and authored the Facade book.
- Mark O’Neill is a CTO at an API company called Vordel
- George Reese is the Hannibal Lector of APIs, eating those that offend him – see Artifactery for his book link.
- Daniel Jacobson is the Netflix API guy and co-author API Strategy (O’Reilly).
- Greg Brail is the Apigee CTO and co-author API Strategy (O’Reilly).
- Dan Woods is a CTO leader and co-author API Strategy (O’Reilly).
- Derek Willis of New York Times API.
- Shanley Kane needs no introduction, not from me anyway!
- Steve Smith from AccuWeather.
- Kin Lane the API Evangelist
- Jim Webber (co-author REST in Practice)
- Savas Parastatidis (co-author REST in Practice)
- Ian Robinson (co-author REST in Practice)
- Martin Fowler (commentator on Richardson’s Maturity Model for REST)
- Leonard Richardson author of Richardson’s Maturity Model for REST.
- API Craft is a Google Group
- Oisin Hurley is Co-founder converser.io
A ordanance survey map of API things on t’interweb
- OpenID 2 Specification (Final)
- Programmable Web – the API directory
- Apigee’s free webinars and eBook on API Facade – don’t agree with the versioning int he URL though…
- Netflix Blog – just because the guys at that company rock, there’s all sorts of goodness there.
- REpresentational State Transfer on Wikipedia
- Roy Fielding on Architectural Styles and the Design of Network-based Software Architectures
- Hypermedia as the Engine of Application State (HATEOS) on Wikipedia
- The REST API Design Handbook by George Reese.
- RFC 2616 HTTP Response Codes on W3.org.
- RFC 6585 Additional HTTP Response Codes on W3.org.
- RFC 2068 HTTP/1.1 Protocol
- RFC 2616 HTTP/1.1 Protocol
- RFC 2396 Uniform Resource Identifiers (URI): Generic Syntax
- RFC 6570 URI Template
- APIs: A Strategy Guide on O’Reilly by Daniel Jacobson, Greg Brail, Dan Woods.
- Kin Lane’s website The API Evangelist where there’s also a link to his co-authored book, The Business of APIs (which I haven’t read yet, sorry Kin!).
- REST APIs must be hypertext-driven on Roy Fielding’s Blog (2008)
- Waka – A replacement for HTTP (in development) by Roy Fielding (slides)
- Rest in Practice (book)
- Leonard Richardson’s Maturity Model – slides from Justice will take a million intricate moves.
- Richardson’s Maturity Model: Steps towards the glory of REST – Martin Fowler’s blog
- Web Application Description Language (WADL) – the REST version of WSDL, on Wikipedia
- WADL on W3C
- Simple Made Easy - video of Rich Hickey explaining simplicity over easiness
- Simple REST Services with Sinatra – slides from Oisin Hurley on doing simple REST in Ruby
- Constructing REST APIs with Rack, Sinatra and MongoDB – more from Oisin Hurley
- Netflix API Documentation
- Explaining the API revolution to your CEO – Dan Woods on Forbes (props James Kane for pointing this out)
- Foundations for Software Architecture – Perry and Wolf
- An Introduction to Software Architectures – Garlan and Shaw
- Routes on Rails – a screencast to show how routes are handled
API frankensteins unite!