vLex · API Governance Rules
vLex API Rules
Spectral linting rules defining API design standards and conventions for vLex.
8 Rules
error 3
warn 5
Rule Categories
vlex
Rules
warn
vlex-operation-ids-camel-case
Operation IDs must use camelCase to match vLex SDK conventions.
$.paths[*][*].operationId
error
vlex-require-subscription-key-security
All vLex Iceberg API operations require a subscription key.
$.paths[*][*]
error
vlex-require-summaries
All operations must have a summary.
$.paths[*][*]
warn
vlex-require-descriptions
All operations and schemas must have descriptions.
$.paths[*][*]$.components.schemas[*]
error
vlex-post-operations-have-request-body
All POST operations must define a requestBody.
$.paths[*].post
warn
vlex-require-401-response
All authenticated operations must define a 401 Unauthorized response.
$.paths[*][get,post,put,patch,delete]
warn
vlex-confidence-fields-use-float
Confidence scores must use type number with format float.
$.components.schemas[*].properties[?(@.description && @.description =~ /confidence/i)]
warn
vlex-v1-api-prefix
All vLex Iceberg API paths must be prefixed with /v1/.
$.paths