Summary

Spencer Schneidenbach talks about REST APIs, what makes a good one, who should design it, how to document it and why developer experience is so important.

Details

Who he is, what he does. Designing an api, the consumer should drive the design, is the developer the main consumer, is the business a customer? What REST is, RPC, nouns not verbs, querying, SEARCH verb, PUT and PATCH, common conventions. Changing how an API works, versioning, version management. Importance of documentation, error code docs, who writes the docs. Consistency, good api design is user experience for developers, Spencer loves Twillo.

Full show notes