Reference
OpenAPI Roadmap
How the generated route inventory can evolve into stricter OpenAPI contracts.
First created Last updated
End-to-end developer runbook
- Step 1 - Confirm the API area: Identify the product area, route module, endpoint path, and consumer before writing or calling code.
- Step 2 - Read the endpoint contract: Check method, auth, parameters, response, errors, side effects, and related docs.
- Step 3 - Prepare authentication and input: Use the right session, bearer token, webhook secret, or internal header. Validate body and query data before sending it.
- Step 4 - Make the request: Call the endpoint from the correct origin and environment. Keep credentials and secrets out of logs.
- Step 5 - Verify response, side effects, and records: Confirm status code, response shape, database records, external side effects, and audit evidence.
- Step 6 - Add tests, docs, and handoff notes: Update route inventory, consumer notes, and certification checks before depending on the change.
Roadmap
- Step 1 - Keep route inventory complete: Method, path, source, and auth scan must remain generated from source.
- Step 2 - Replace unknown schemas: Manually inspect handlers and add proven request and response schemas.
- Step 3 - Add examples: Capture safe curl and TypeScript examples for each endpoint family.
- Step 4 - Add contract tests: Verify generated docs against route behavior.
- Step 5 - Emit OpenAPI: Convert proven endpoint contracts into an OpenAPI document only after unknowns are resolved.