Validate OpenAPI 3.2, 3.1, 3.0 & Swagger 2.0 specifications. Paste JSON/YAML, upload files, or fetch from URL.
1Paste or upload your OpenAPI spec and click Validate to see a live preview.
Start free for quick checks, or go Developer when validation is part of your release process. Drop your API key into GitHub Actions, GitLab CI, or cURL — examples below.
For more details, please see our documentation on openapi-validator.apinotes.io.
Sign up — it takes 10 seconds
No credit card requiredFree
20/mo
1 API key
Best for personal projects, proof-of-concept automation, and first-time setup.
Developer
1,000/mo
5 API keys
Ideal for shared environments, branch protection, and shipping validation on every merge.
Ensuring your API specification validates against the official standard is crucial for generating accurate documentation and SDKs.
Invalid JSON or YAML formatting
Adherence to OAS 3.0, 3.1 or 3.2
Required properties checks
OpenAPI 3.2
Latest release, fully supported
OpenAPI 3.1
Latest standard with webhooks
Swagger 2.0 & OAS 3.0
Full backward compatibility
Four simple steps to validate your OpenAPI specification.
Paste or Upload
Copy your OpenAPI JSON/YAML content or upload a file directly.
Instant Feedback
Our validator parses your spec against official schemas in real-time.
Fix & Retry
View detailed error messages to quickly resolve issues.
Preview & Publish
Once valid, preview your documentation and publish it instantly.