API Discovery done right: Engaging the right people with your APIs.
summary
Built and run for three years as a public API portal for a customer, the project maps features to four access channels using the API consumer access model to decide scope and audience. Registry accepts OpenAPI and AsyncAPI definitions, docs render with Swagger UI, APIs are gated by Spectral linting rules, login uses OAuth and supports self-service credentials, sandboxes require separate try-out servers, and a CMS drives product pages and checkout — mapping reveals when developer features crowd out business needs.
AI-written summary · about
chapters (11)
- 0:00API discovery strategies
- 1:30Speaker background and project context
- 3:20API consumer access model
- 5:05Feature mapping
- 7:15Landing page features
- 9:21Credentials integration
- 10:46Marketplace features
- 12:37Portal personas
- 15:08Technical to business focus
- 17:39API portal design takeaways
- 20:34Q&A
related talks
24mAPI Discovery: Turning Hidden APIs into Strategic Assets
26mFrom project to reality let's explore some API
24mAPI design is where culture and tech meet each other
28mAPI Productisation - shift RIGHT to Better Product Resilience
52mAPI Governance at Scale
19mSecure and accelerate APIs' lifecycle with the OpenAPI specification
27mEnterprise API management in agile integration
39mAPI Development in 2017