How to Win Friends with API First
summary
Postman reports 17 million users and a 28,000-person survey showing 11% uncertainty about API first; API‑first defines interfaces with OpenAPI 2/3 so teams generate docs, mock servers, tests and even server stubs from a single spec, letting frontends hit live mocks while backends are built and swapped by URL. Consumer‑driven contract testing runs consumer tests in CI to block breaking changes. Companies like Etsy and Netflix moved to API‑first to avoid repeated rewrites and bottlenecks.
AI-written summary · about
chapters (20)
- 0:00API first development
- 1:05Why this talk
- 3:15Defining API first
- 5:25Code first problems
- 7:34API first benefits
- 9:47Reducing bottlenecks
- 11:14Early validation
- 12:40API first and chaos engineering
- 14:51Industry examples
- 15:32API first tools
- 16:35API specifications
- 19:50Team collaboration
- 20:12Mock servers
- 22:40Contract testing
- 24:48Postman’s API first
- 25:33Key points
- 26:37When API first is worth the effort
- 27:38API first benefits
- 28:20Challenges and resources
- 29:02Learn more
related talks
25mThe Life Changing Magic of Becoming API First
30mPostman Platform Overview: Be API-First, Not API-Last
05mAPI-First Development: Future-Ready Systems
30mAPI Code First vs Design First
24mThe API-First World is for Non-Developers, too!
11mThe democratisation of APIs
34mAPIs Are Eating the Universe
26mRevolutionizing Business with API-First Strategy: Key Insights