OpenAPI repair

Use a supported OpenAPI version

This checker supports OpenAPI 3.0.0 through 3.0.4 only.

Match the finding

These titles and messages come from this local checker. They are not AWS service error quotes.

Cause and scope

Swagger 2.0, OpenAPI 3.1, and other versions have different structures or semantics. The checker does not convert them and disables repair outside its supported version range.

What to do

Use tooling designed for the original version. If conversion is necessary, use a trusted conversion workflow and review the resulting schema, references, and security before checking it here.

  1. Check the top-level openapi or swagger field to confirm the actual specification version.
  2. Keep the original and choose a version-compatible workflow or an explicitly reviewed conversion.
  3. Validate the result independently before using this OpenAPI 3.0 checker.

Diagnostic document: an unsupported version stops this checker

openapi: 3.1.0
info:
  title: Example API
  version: '1.0.0'
paths: {}

The 3.1.0 declaration is enough to trigger this checker’s version finding before repair. This is a local support boundary, not a claim that the document is invalid OpenAPI. Use tooling for its actual version; do not change the label to bypass the check.

Avoid a misleading fix

Do not simply change the version string. OpenAPI 3.1 schema features, including its null representation, cannot be downgraded by relabeling the document.

Check your complete file locally

Choose one OpenAPI 3.0 JSON or YAML file, diagnose the findings, and review any eligible security-copy preview before downloading. No file upload or account is needed.

Open the free OpenAPI checker →

Related findings

Sources and scope

Scope: this local checker, API Gateway REST APIs, and OpenAPI 3.0. Guidance reviewed 4 October 2026. A passing check does not guarantee import or runtime behavior.