OpenAPI for Web Developers
summary
OpenAPI gets used as a real pipeline artifact here not just a spec file: code can generate from code or be sniffed by Optic to bootstrap a description, overlays apply repeatable edits so teams can overlay edits for different outputs, mock servers (Prism micro) exercise multiple response examples, SDK generators produce client libraries, and contract tests (WireMock or contract runners) detect API drift. The useful deliverables are the populated OpenAPI, the mock sandbox that worked, and the CI checks that catch breaking changes.
AI-written summary · about
chapters (9)
- 0:00OpenAPI introduction
- 3:56Why OpenAPI matters
- 9:31Generate OpenAPI from APIs
- 15:35Improve OpenAPI with overlays
- 21:42Generate SDKs from OpenAPI
- 27:03API governance standards
- 31:15Mock servers and sandboxes
- 36:08Avoid API drift with testing
- 40:22OpenAPI community and standards
related talks
20mOpenAPIspec
09mEverything You Need to Know About OpenAPI 3.0
05mAPI-First Development: Future-Ready Systems
31mBeyond OpenAPI: API Workflows That AI Agents Can Actually Execute
43mValidating Entire User Journeys by Isolating Front Ends using OpenAPI
53mUncovering Swagger/OpenAPI
32mCode to contract to code: making ironclad APIs
38mZen And The Art Of Automanually Creating API Documentation - An Inquiry Into Process