api-spec-generator

To keep OpenAPI specs in sync with code changes automatically, parse API definitions directly from source code to detect surface changes and merge updates into openapi.yaml. This ensures documentation accurately reflects the latest tRPC, REST, or GraphQL implementations.

Yes, you can generate Bruno collections from an existing or updated OpenAPI specification. By parsing your API definitions and regenerating the spec, the process outputs Bruno files for testing alongside the updated openapi.yaml file.

Yes, API documentation generation works with tRPC and GraphQL. The process detects changes across tRPC routers, REST endpoints, and GraphQL schemas, then generates and merges OpenAPI 3.x specs for these multiple service types.

The best way to update REST endpoint docs during CI/CD is to run an automated detection process against your service repository. This parses API changes from code, merges updates into openapi.yaml, and outputs Bruno collections plus changelog entries.

No, you do not need a specific backend language to automate OpenAPI spec generation. The process applies across Node.js, Go, and Python backends, allowing you to parse definitions and keep docs aligned with code regardless of these stacks.

Your Bruno test collections fail to match updated API endpoints because they are out of sync with code changes. Regenerating Bruno files by parsing the latest API definitions ensures your test collections align with the current OpenAPI spec.