An Operating Model for API Platforms
summary
NHS England builds a One‑Stop API platform with an API satisfaction survey (annual, plotted 2020–2023) and a user‑needs program that targets both API consumers and producers. The platform uses appg Edge, local stack, kloo, Prometheus and Grafana, plus feature backlog tooling, and creates an internal deployment service called proxygen that generates proxies from OpenAPI and offers a CLI. Proxygen cuts lead time by 75% and halves onboarding support; internal polling shows 43% cannot find API descriptions and 56% see design‑review bottlenecks.
AI-written summary · about
chapters (14)
- 0:00API platform operating models
- 1:51API delivery at scale
- 3:37API platform success metrics
- 4:21Two-customer mindset for API teams
- 5:45NHS England API platform case study
- 7:48API producer benefits and user needs
- 9:29NHS England API platform tools
- 10:31Measuring API success with surveys
- 12:20API delivery challenges poll
- 15:08NHS England two-customer lessons
- 16:16API delivery abstractions
- 17:20NHS England ProxyGen solution
- 20:30API abstraction lessons
- 21:15API platform best practices
related talks
30mBuilding high-performance API platform teams
42mThe future of API (Platform) architecture
25mBeyond API Governance: Run your API org like a lean startup
27mEnterprise API management in agile integration
25mBoost API Success: Key to Transparency & Accountability
24mFixing API Chaos: A Practical, Open Method to Structure API Work
32mThe 7 commandments for a successful API Program
26mFrom project to reality let's explore some API