Revert · API Governance Rules
Revert API Rules
Spectral linting rules defining API design standards and conventions for Revert.
10 Rules
error 2
warn 6
info 2
Rule Categories
revert
Rules
warn
revert-operation-id-camel-case
All operationIds must use camelCase format consistent with Revert SDK generation
$.paths.*.*
warn
revert-tags-title-case
All tags must use Title Case
$.tags[*].name
error
revert-tenant-id-header-required
All endpoints except /connection must include x-revert-t-id header
$.paths[?([email protected](/^\/connection$/))].*
error
revert-api-token-auth
All endpoints must declare x-revert-api-token security
$.paths.*.*
warn
revert-response-status-field
All 200 responses should include a status field in the schema
$.paths.*.*.responses.200.content.application/json.schema.properties
warn
revert-pagination-cursor-consistency
List endpoints returning paginated results must include next and previous cursor fields
$.paths[?(@property.match(/^(?!.*\{id\}).*$/))].get.responses.200.content.application/json.schema.properties
info
revert-version-prefix
All API paths should follow the established /crm/, /ticket/, /chat/, /accounting/ namespace pattern
$.paths
warn
revert-no-trailing-slash
API paths must not end with a trailing slash
$.paths
warn
revert-kebab-case-paths
Path segments must use kebab-case
$.paths
info
revert-additional-fields-support
Request bodies for create/update operations should include an additional field for non-unified data
$.paths.*.post.requestBody.content.application/json.schema.properties