Apidays Virtual Helsinki - Erik Wilde, Axway
summary
Argues that API governance succeeds when an organization builds three concrete pieces: insights into the API landscape (labels as metadata and a separate visibility layer so multiple gateways and external APIs are discoverable), interfaces enforced by minimal constraints not rules (requirements like “secure this API” but allow any gateway that proves compliance), and nudging through platforms and gateways to steer teams toward reuse—result is fewer hidden dependencies and faster feature delivery.
AI-written summary · about
chapters (17)
- 0:00Intro
- 2:00Background
- 2:19Catalyst Team
- 3:19Api Academy
- 4:33Insights
- 6:24Api Architecture
- 8:45Governance
- 11:35Insight
- 13:30Labels
- 15:30Interfaces
- 15:55Constraints
- 18:27Decouple teams
- 19:24Nudging
- 20:10Engineering
- 20:37Nudge
- 23:04Recap
- 25:32Wrapup
related talks
27mPillars of the Successful API Governance
27mAPI Economy and Ecosystem
26mAPIs are the new skin of your organisation
21mMastering API Design: Why Community Matters
26mAPI Governance: The Latest Trends Making Teams Love API Standardization.
25mAutomating API Governance
40mThe API mindset: tech, product, business and legal
27mBuilding Great Web APIs