Veryfi · API Governance Rules
Veryfi API Rules
Spectral linting rules defining API design standards and conventions for Veryfi.
10 Rules
error 2
warn 7
info 1
Rule Categories
veryfi
Rules
warn
veryfi-operation-ids-camel-case
Operation IDs must use camelCase as per Veryfi API conventions
$.paths[*][get,post,put,patch,delete].operationId
warn
veryfi-paths-must-use-partner-prefix
All paths must be under /partner/ namespace
$.paths[*]~
error
veryfi-require-client-id-security
All operations must declare clientId security
$.paths[*][get,post,put,patch,delete]
warn
veryfi-document-responses-must-be-201
Document creation endpoints must return 201 Created
$.paths[*].post.responses
warn
veryfi-require-operation-description
All operations must have a description
$.paths[*][get,post,put,patch,delete]
warn
veryfi-require-operation-tags
All operations must have at least one tag
$.paths[*][get,post,put,patch,delete]
warn
veryfi-error-responses-must-reference-schema
Error responses must include a schema
$.paths[*][get,post,put,patch,delete].responses['4*','5*'].content['application/json']
info
veryfi-require-api-contact
API info must include contact information
$.info
warn
veryfi-document-id-must-be-integer
Document IDs in paths must be integers
$.paths[*][get,delete].parameters[?(@.name == 'documentId')].schema
error
veryfi-post-requests-must-have-body
POST operations must have a request body defined
$.paths[*].post