Highlight (highlight.io) · API Governance Rules
Highlight (highlight.io) API Rules
Spectral linting rules defining API design standards and conventions for Highlight (highlight.io).
13 Rules
error 8
warn 5
Rule Categories
highlight
Rules
error
highlight-info-title-required
All Highlight OpenAPI specs MUST include info.title.
$.info
error
highlight-info-description-required
All Highlight OpenAPI specs MUST include a non-empty info.description.
$.info
warn
highlight-info-contact-required
All Highlight OpenAPI specs MUST include info.contact with name and url.
$.info.contact
warn
highlight-info-license-apache-2-0
Highlight OpenAPI specs SHOULD declare the Apache 2.0 license for ingestion endpoints.
$.info.license
error
highlight-servers-required
Every Highlight OpenAPI spec MUST list at least one server.
$
error
highlight-server-https-required
Hosted Highlight ingestion endpoints MUST use https.
$.servers[?(@.url =~ /highlight\.io/)]
error
highlight-operation-id-camelcase
Operation IDs MUST be camelCase.
$.paths[*][*].operationId
warn
highlight-operation-summary-title-case
Operation summaries MUST start with a capital letter (Title Case).
$.paths[*][*].summary
error
highlight-operation-description-required
Every operation MUST include a description.
$.paths[*][*]
error
highlight-operation-tags-required
Every operation MUST be tagged.
$.paths[*][*]
error
highlight-response-200-or-2xx-required
Every operation MUST document a 2xx response.
$.paths[*][*].responses
warn
highlight-error-responses-recommended
Highlight ingestion endpoints SHOULD document 400 and 429 responses.
$.paths[*][post].responses
warn
highlight-otlp-content-types
OTLP endpoints MUST accept application/json and SHOULD accept application/x-protobuf.
$.paths[?(@property =~ /v1\/(traces|logs|metrics)/)][post].requestBody.content