Vital · API Governance Rules
Vital API Rules
Spectral linting rules defining API design standards and conventions for Vital.
9 Rules
error 3
warn 5
info 1
Rule Categories
vital
Rules
error
vital-info-title-junction-or-vital
API title must be "Junction API", or a Vital-prefixed sub-API title.
$.info.title
warn
vital-info-contact-url-junction-docs
API contact.url should point to docs.junction.com.
$.info.contact
warn
vital-servers-regional-set
Servers list should include US and EU regional production and sandbox base URLs.
$.servers
error
vital-server-url-allowed
Server URLs must use the api.{region}.junction.com or api.sandbox.{region}.junction.com pattern.
$.servers[*].url
error
vital-paths-versioned
All paths must be versioned under /v1/, /v2/, /v3/, or grouped namespace (/aggregate/, /lab_report/).
$.paths[*]~
warn
vital-operation-operation-id-snake-case
Operation IDs follow snake_case (Fern convention).
$.paths[*][*].operationId
warn
vital-operation-tags-required
Every operation should declare at least one tag.
$.paths[*][get,post,patch,put,delete]
info
vital-operation-summary-title-case
Operation summaries use Title Case.
$.paths[*][*].summary
warn
vital-security-api-key-header
Document an X-Vital-API-Key apiKey security scheme.
$.components.securitySchemes