The API Specficiations Toolbox
summary
Shows a concrete toolbox: Slack’s Web API has an OpenAPI v3 file (paths, components, JSON Schema payloads) and its Events API has an AsyncAPI document (servers, channels, payload schemas) so real-time and HTTP contracts coexist. JSON Schema is used for validation (including a schema-for-json-schema), Swagger UI and Postman are used for docs/mocks/tests, Postman collections can be generated from OpenAPI and add pre/post scripts and environments, apis.json indexes all artifacts. Notes: Swagger dated ~2010–11, AsyncAPI started ~2016–17.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:26Api Evangelist
- 1:57Open Api
- 2:46Apis Json
- 3:58Open Api Slack
- 10:07Async Api Specification
- 10:19Async Api
- 12:02Channels
- 18:22Postman Collections
related talks
31mUnifying OpenAPI & AsyncAPI : Designing JSON Schemas+Examples.
27mAsyncAPI & The future of API specs
19mSecure and accelerate APIs' lifecycle with the OpenAPI specification
44mAsyncAPI – Swagger for asynchronous APIs
01h 03mOpenAPI and AsyncAPI, when to use which and why
21mLet there be docs!
31mOpenAPIs are everywhere
19mUnlock API and Data – The Power of Data Model and Governance