Validate an OpenAPI specification

POST 
/api/v2/openapi/validate/

Validate an OpenAPI specification against the same checks Biel runs when it indexes your spec, including $ref resolution. A 200 means the next sync will parse the spec; a 422 returns the validation errors it would fail with.

Designed for CI/CD: publish your spec, call this endpoint, and fail the pipeline on a non-2xx status. This catches changes that would break API indexing before Biel's next sync does.

Submit the spec either by url (Biel fetches it and resolves relative $refs against it) or inline as content (JSON or YAML).

Required permission: none. Any valid API key works.

Request

Responses

200

The specification is valid. A sync will parse it.

400

Validation error. Field-level errors keyed by field name.

403

Forbidden. Missing permissions.

422

The specification failed to fetch, parse, or validate.