What will the next generation of API Portals look like?
summary
Claim: next-generation API portals shift from developer-only docs to developer-enabled products with distinct roles (business decision maker vs technical user), baked-in KPIs and monetization. Implementation options: vendor off-the-shelf, custom agency, or SaaS. A working model is an API portal as a service that is technology-agnostic, supports multiple gateways and identity providers, exposes a digital marketplace for subscription products, and offers role-based views and analytics; several pilot customers run live by mid‑2021.
AI-written summary · about
chapters (9)
- 0:00Intro
- 1:17API Portals
- 2:25Problems with API Portals
- 3:55Customer and User
- 5:00Developer Experience
- 9:46Make them consumable
- 14:07Should we use both
- 17:27Future of API Portals
- 21:32APIable
related talks
15mAPI Portals Reimagined: Past, Present, and Future Trends
25mUnlocking API Potential: The Power of Developer Portals
27mWhy your API portal is so bad and what you can do about it
27mLatest Trends in API Management in 2019
28mAPIs should be products, devportals too - or shouldn't they?
29mThe Future of API Integration
27mDemocratizing developer experience
17mDeveloper Portals, API Catalogs, and Marketplaces