The Life Changing Magic of Becoming API First
summary
A concrete claim: designing APIs before code reduces rework and enables parallel development by letting docs, tests and clients start against mock servers generated from a spec. Evidence: a Postman survey of ~13,000 respondents, Postman platform with 17 million users, and rising use of OpenAPI v3. Tactics shown: generate mocks from an OpenAPI spec, run consumer‑driven contract tests to block breaking changes, and auto‑generate docs/tests/servers from the schema.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:24What is API first
- 3:11API first vs API last
- 6:22Problems with code first
- 7:50API first in practice
- 11:21API specifications
- 15:58Mock servers
- 18:13Consumer-driven testing
- 21:00Key takeaways
- 22:25Is API first for everyone
related talks
30mHow to Win Friends with API First
30mAPI Code First vs Design First
05mAPI-First Development: Future-Ready Systems
30mPostman Platform Overview: Be API-First, Not API-Last
43mWhy You Should Be Doing Contract-First Development
16mAPI-First Development with OpenAPI — You Should Practice It!?
26mRevolutionizing Business with API-First Strategy: Key Insights
27m"Building Elegant API Contracts: From Zero to Hero"