The API Design Strategy You Need for Growth

on YouTube ↗27m

" summary

Shows that API design must match business model by walking a proptech integration failure where a mandatory field surfaced via get work order picklists (opaque IDs) and broke a background sync. Builds a fictional order‑fulfillment API and compares an all‑in‑one endpoint to a modular model, then replaces shipping enums with a provider resource to avoid breaking changes and enable global scaling and transaction pricing. Demonstrates using Criteria diagrams (free, exports OpenAPI) to prototype before code.

AI-written summary · about

" chapters (7)

1. 0:00Introduction
2. 4:42API design and business
3. 9:17API provider vs client
4. 13:35Revenue with pricing
5. 17:09Global API scalability
6. 21:24API-first workflows
7. 26:29Closing

" related talks

• 21mPragmatic Strategies for Global API IntegrationRobert Prince · apidays London 2023
• 27mAvoid These API Design Mistakes for Better Business IntegrationPatrick Brosse · apidays London 2023
• 27mBuilding Great Web APIsMike Amundsen · apidays New York 2020
• 21mScaling API DesignJason Harmon · Platform Summit 2014
• 24mFixing API Chaos: A Practical, Open Method to Structure API WorkMarjukka Niinioja · apidays India 2026
• 26mRevolutionizing Business with API-First Strategy: Key InsightsJean Burellier · apidays New York 2023
• 49mBuilding Software Better: API Lifecycle Management for DevelopersErik Wilde · GOTO Amsterdam 2024
• 26mMastering API Strategies for Digital TransformationClaire Barrett · apidays London 2023