OpenAPI error directory
Fix common OpenAPI validation errors.
Eight focused guides with broken YAML, the exact reason each document fails, corrected YAML, version differences, and a concrete validation step.
-
How to fix duplicate operationId errors in OpenAPI
Fix a duplicate operationId with a minimal failing spec, a corrected example, version notes, and two concrete validation paths.
-
How to fix a missing path parameter declaration in OpenAPI
Declare every URL template variable as an OpenAPI path parameter. See minimal broken YAML, the exact rule, and the corrected spec.
-
How to fix "path parameter must be required" in OpenAPI
Every OpenAPI path parameter must set required: true. See the failing YAML, the reason, the corrected YAML, and validation steps.
-
Fix nullable syntax errors in OpenAPI 3.0 and 3.1
Use nullable: true in OpenAPI 3.0 and a null type in OpenAPI 3.1. See the failing YAML, corrected YAML, and validation command.
-
How to fix "exclusiveMinimum must be boolean" in OpenAPI
Fix an exclusiveMinimum type mismatch when a numeric OpenAPI 3.1 constraint appears in an OpenAPI 3.0 document.
-
How to fix an invalid response code key in OpenAPI
Replace invalid response labels such as 200 OK with a quoted status code, an allowed range, or default. Includes 3.0 and 3.1 notes.
-
How to fix unresolved $ref errors in OpenAPI
Fix an OpenAPI $ref that points to a missing component. See broken and corrected YAML, version notes, and validation steps.
-
How to fix an OpenAPI array schema missing items
Add an items schema to an OpenAPI array. See why OpenAPI 3.0 rejects it, how 3.1 differs, and how to validate the fix.