Validate & Lint Overview

When you import an API definition, APIMatic runs validation and linting checks on it and reports every issue it finds. Fixing these first gives you better APIMatic SDKs, docs, and portals.

Validate with the APIMatic CLICopy Anchor Link

apimatic api validate
apimatic api validate --file=<path>
apimatic api validate --url=<url>

With no flags, the command validates the API definition in your project's src directory. Run it from the folder that contains src, or pass that folder with --input. To validate a single file instead, use --file or --url. For every flag, see api validate in the CLI Reference.

Validate in VS CodeCopy Anchor Link

To validate locally while you edit, use APIMatic for VS Code. It checks your definition against APIMatic's validation and linting rules as you save, explains each issue, and can fix common issues automatically.

Validate pull requests on GitHubCopy Anchor Link

The APIMatic OpenAPI Linter GitHub App validates the OpenAPI definitions in your repository on every pull request and reports the results as a PR comment and a GitHub check.

Rules and rulesetsCopy Anchor Link

Each APIMatic check is a rule, and rules are grouped into rulesets. A rule is identified by its ruleset ID and rule ID, for example apimatic-preliminary-validation:required-server-url, or by a rule code such as APIMATICPRE_V036.

There are two kinds of rules:

• Validation rules make sure your API definition conforms to its format and is technically correct.
• Linting rules are style checks and recommendations. They improve the definition without affecting whether it's valid.

See Rulesets Overview for every ruleset and rule, by format. To skip linting rules or change their severity, see Configure Validation.

Rules check two things:

• Syntax: the structure of expressions and statements is valid.
• Semantics: the definition makes sense in context.

Severity levelsCopy Anchor Link

Messages are reported at one of four levels, from most to least severe: