Uber · API Governance Rules
Uber API Rules
Spectral linting rules defining API design standards and conventions for Uber.
11 Rules
error 2
warn 9
Rule Categories
uber
Rules
warn
uber-operation-id-camel-case
Operation IDs must use camelCase.
$.paths[*][get,post,put,patch,delete].operationId
warn
uber-path-kebab-case
API paths must use kebab-case segments.
$.paths[*]~
warn
uber-summary-title-case
Operation summaries must use Title Case.
$.paths[*][get,post,put,patch,delete].summary
warn
uber-has-tags
All operations must have at least one tag.
$.paths[*][get,post,put,patch,delete]
error
uber-has-operation-id
All operations must have an operationId.
$.paths[*][get,post,put,patch,delete]
warn
uber-has-description
All operations must have a description.
$.paths[*][get,post,put,patch,delete]
warn
uber-200-response-body
Successful GET operations should return a response body schema.
$.paths[*].get.responses.200
warn
uber-bearer-auth-required
Uber APIs require OAuth 2.0 bearer token authentication.
$.paths[*][get,post,put,patch,delete]
warn
uber-version-prefix
Uber server URLs should include a version prefix.
$.servers[*].url
warn
uber-no-trailing-slash
API paths must not have trailing slashes.
$.paths[*]~
error
uber-required-info-fields
API info block must include title, description, version, and contact.
$.info