Check OpenAPI 3.0 before an API Gateway REST import.
Find selected OpenAPI 3.0 and AWS API Gateway REST issues. Free, local to your browser, and no account needed.
- 1Choose file
- 2Review findings
- 3Export
Start with your OpenAPI file
Drop a JSON or YAML file here, or choose one from your device.
OpenAPI 3.0 only · One file · Up to 1 MiB
No upload, account, or API key. External references are never fetched.
Start with the finding you’re seeing
Each guide explains the cause, a minimal example, and a safe next step. The wording below comes from this checker; AWS console messages may differ.
- Root security is ignored by API GatewayPreserve operation overrides while making inherited security explicit
- External reference is blockedBundle the actual definition without losing the referenced contract
- Schema nullable is unsupportedKeep null, absent, and normal values distinct
- Internal reference does not resolveCheck the pointer, its target, and component kind
Passed an OpenAPI validator but still blocked? Why valid OpenAPI fails AWS API Gateway import
Try cases you can verify
Download nine synthetic inputs with expected findings, exact preview outputs, and checksums. See what changes, what stays untouched, and what these tests do not prove.
From finding to a reviewed file
- Diagnose locally. Choose one OpenAPI 3.0 JSON or YAML file, up to 1 MiB, or try the synthetic sample.
- Review the cause. Follow source locations and targeted guides. Unsupported or potentially lossy changes stay manual.
- Preview, then download. If eligible, review exact root-security copies before downloading a new file. Existing security overrides stay unchanged.
This tool checks selected issues. It does not connect to AWS, create an authorizer, convert Swagger 2.0 or OpenAPI 3.1, or guarantee import success. Read the supported checks and limits