Vessel · API Governance Rules
Vessel API Rules
Spectral linting rules defining API design standards and conventions for Vessel.
10 Rules
warn 7
info 3
Rule Categories
vessel
Rules
warn
vessel-operation-ids-camel-case
Operation IDs must use camelCase as per Vessel API conventions
$.paths[*][get,post,put,patch,delete].operationId
warn
vessel-require-api-token-security
All operations must declare apiToken security scheme
$.paths[*][get,post,put,patch,delete].security
info
vessel-post-responses-should-return-200
Vessel API uses POST for most operations and returns 200
$.paths[*].post
warn
vessel-require-operation-description
All operations must have a description
$.paths[*][get,post,put,patch,delete]
warn
vessel-require-operation-tags
All operations must have at least one tag
$.paths[*][get,post,put,patch,delete]
warn
vessel-ids-should-be-strings
All ID fields in schemas should be type string (Vessel normalizes all IDs to strings)
$.components.schemas[*].properties.id
info
vessel-dates-should-be-datetime
Date fields should use date-time format (Vessel normalizes all dates to ISO 8601)
$.components.schemas[*].properties[*At]
warn
vessel-error-responses-should-have-schema
Error responses must include a content schema
$.paths[*][get,post,put,patch,delete].responses['4*','5*'].content['application/json']
info
vessel-require-contact-info
API info must include contact information
$.info
warn
vessel-passthrough-must-have-request-body
The passthrough endpoint must define a request body
$.paths['/passthrough'].post