Postman Platform Overview: Be API-First, Not API-Last
summary
Argues that API‑first is a strategic shift not just design vs code and that organizations must use OpenAPI AsyncAPI JSON Schema and generate Postman collections from contracts so definitions are discoverable, testable and versioned; recommends test‑driven contract checks as modular collections that run from design through production; cites cloud pioneers (EC2 S3) as API‑first examples and notes regulatory pushes like PSD2 and FHIR plus CFPB moves; promises better portability, observability and faster iteration when APIs are treated as first‑class products.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:53What is API-First?
- 4:11What Is an API?
- 9:50How Do You Do API-First?
- 12:12How to Sustain API-First?
- 15:47Why API-First?
- 18:03Scope of API-First
- 21:02The Impact of API-First Change
- 23:37Are You API-First or API-Last?
- 26:38Resources
related talks
30mHow to Win Friends with API First
25mThe Life Changing Magic of Becoming API First
28mThe API is the Platform
26mRevolutionizing Business with API-First Strategy: Key Insights
24mThe API-First World is for Non-Developers, too!
26mCollaborate Like You Mean it: The End of Siloed API Development
24mBuilding APIs Together: How to Embrace a Multi-Player Strategy.
30mAPI Code First vs Design First