Building APIs your users will want to use
summary
Shows concrete moves: change a C app to emit snake_case JSON serializer so Python and C responses match, wrap results in a response envelope with data messages errors and HATEOAS links, use OpenAPI 3.0 + Postman/Newman contract tests to prove Python and ASP NET Core endpoints return the same schema, adopt RFC 7807 for consistent errors, rely on ETags for caching and stateless requests, and route versions via an API gateway so demos of mixed-language services validate successfully.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:09Why users hate APIs
- 3:42Consistent API design
- 6:30Demo: property naming
- 10:04Response envelopes
- 12:57REST and URI design
- 15:49Error formats with RFC 7807
- 18:14Hypermedia and HATEOAS
- 21:44Clear property names
- 22:28Spec-first design
- 28:54Repeatable and stateless APIs
- 31:20Versioning APIs without breaking contracts
- 34:28Demo: safe migrations
- 37:45Long-term API thinking
- 39:30Q&A: URI vs header versioning
related talks
27mBuilding Great Web APIs
27m"Building Elegant API Contracts: From Zero to Hero"
35mBuilding Your API for Longevity
41mThe making of a great API
27mGetting developers hooked on your API
59mDriving better outcomes through API first development
40mGive It a REST – Tips for Designing and Consuming Public API’s
35mPrinciples of Awesome APIs and How to Build Them