Veracode · API Governance Rules
Veracode API Rules
Spectral linting rules defining API design standards and conventions for Veracode.
11 Rules
error 5
warn 5
Rule Categories
veracode
Rules
error
veracode-hmac-auth-defined
Veracode APIs must define HMAC security scheme
$.components.securitySchemes[*]
error
veracode-path-prefix
Veracode API paths must use /appsec/ or /api/authn/ prefix
$.paths[*]~
error
veracode-operation-id-required
All operations must define an operationId
$.paths[*][get,post,put,patch,delete]
warn
veracode-operation-id-camel-case
operationId should use camelCase
$.paths[*][get,post,put,patch,delete].operationId
warn
veracode-summary-title-case
Operation summaries must use Title Case
$.paths[*][get,post,put,patch,delete].summary
error
veracode-summary-required
All operations must have a summary
$.paths[*][get,post,put,patch,delete]
error
veracode-401-response
All operations must document 401 Unauthorized response
$.paths[*][get,post,put,patch,delete].responses
warn
veracode-guid-uuid-format
Properties named 'guid' should use uuid format
$.components.schemas[*].properties.guid
hint
veracode-hal-embedded-pattern
Collection responses should use HAL _embedded structure
$.components.schemas[*]
warn
veracode-api-version-in-path
API paths should include version (v1, v2, etc.)
$.paths[*]~
warn
veracode-info-contact
API info must include contact information
$.info