Improve your API and OpenAPI
summary
OpenAPI drives a design‑first HTTP API workflow that produces docs, mocks and automated checks: the rock paper scissors example yields a spec, Redoc HTML docs, a Stoplight GUI editor, Prism mock server that enforces required fields, and Spectral plus an OpenAPI spec validator in CI. Middleware uses php league validators to return 422 for bad requests and 500 for invalid responses. Schemathesis generates 306 tests against one endpoint. This yields mock servers and validation middleware that actually catch integration and contract errors before production.
AI-written summary · about
chapters (18)
- 0:00Start
- 10:06openapi.yaml
- 11:23Metadata
- 12:25Endpoints
- 17:11Build on top of other components
- 18:31Responses responses
- 20:27Editing
- 23:56Linting & validation CLI tools: Spectral, openapi-spec-validator, etc.
- 24:48Validation error
- 25:29Docs
- 28:30Mock server
- 29:39Make API calls
- 30:45Validation The schena section can be used to validate the request and response
- 34:19Test Request
- 35:01Test Response
- 35:27Successful validation
- 37:27Compliance Testing
- 39:09Other Interesting Tools • Optic: BC Break Detection
related talks
35mFake It Before You Make It: Mocking Your Way to Better HTTP APIs
36mTesting via OpenAPI, or How to Validate Your Documentation
30mAPI Evolution With CRDs: Best Practices For Authoring & Fuzz Testing APIs
26mTips and tricks for writing API Tests
29mBeyond OpenAPI and AsyncAPI: AI agents wrote the spec, code, and tests - now w…
30mBreak the API Test Data Bottleneck: Real Scenarios on Real Systems
24mAugmented API Design Review with OpenAPI and Spectral
23mSolving Challenges in API Testing to Achieve More Agile Development