OpenAPI OperationId Linter & Fixer
Reports missing and duplicate operationId values and can generate IDs for missing operations. It does not enforce casing conventions.
About this openapi operationid linter & fixer
Reports missing and duplicate operationId values and can generate IDs for missing operations. It does not enforce casing conventions Validates and converts interface schemas client-side without transmitting private endpoint specifications.
API contract & interface schema logic
Parses, validates, and transforms OpenAPI Specification (OAS) 3.0.x and 3.1.x contracts into client code, documentation, and Model Context Protocol (MCP) tool manifests. Features a path-scoped recursive dereferencing engine that expands shared $ref schema components (such as address schemas shared across billing and shipping) while reliably halting true circular loops. Validates YAML/JSON specifications against official OpenAPI metamodels with line-numbered syntax diagnostics.
Worked schema conversion scenario
Scenario: Report a missing and a duplicate OpenAPI operationId.
Sample input:
Processing: Inspect supported HTTP operations, track IDs already seen, and optionally synthesize IDs only for missing operations in fix mode.
Illustrative output:
Schema version & syntax constraints
Fix mode fills missing IDs with collision-free suffixes but leaves preexisting duplicate IDs unchanged. Lint checks supported operations only; neither mode validates naming conventions or the full OpenAPI document.
API specifications and schema models in OpenAPI OperationId Linter & Fixer reflect OpenAPI and JSON Schema standards. Verify generated schemas against your runtime validator.
Client-side schema processing boundary
Schema analysis and protocol mapping in OpenAPI OperationId Linter & Fixer execute locally in the browser tab without uploading endpoint definitions.
OpenAPI Specification & JSON Schema standards
OpenAPI Specification standards and JSON Schema draft definitions:
OpenAPI OperationId Linter & Fixer verification · Audit standards
How to use it
- Paste OpenAPI JSON or YAML; optionally set secondary mode to fix/generate.
- Report missing and duplicate operationIds, or synthesize IDs for missing operations in fix mode.
- Read JSON issues or the rewritten YAML.
Frequently asked questions
What does OpenAPI OperationId Linter inspect?+
It walks recognized HTTP operations in the supplied OpenAPI paths and reports missing or duplicate operationId values with their method and path.
Can you show an input and its result?+
A GET /pets operation without an operationId returned valid false, operationCount zero, and the explicit missing-operationId issue.
Can the page automatically generate missing IDs?+
Secondary fix/generate mode synthesizes IDs only for missing supported operations. It reserves all existing IDs and adds _2, _3 and later suffixes to new collisions. Existing duplicate IDs remain untouched; ordinary lint mode returns JSON issues.
What does a clean report prove?+
It only shows that recognized operations had nonduplicate IDs in the supplied document. It does not generate an SDK, validate every OpenAPI rule, or publish a changed specification.