United Technologies · API Governance Rules
United Technologies API Rules
Spectral linting rules defining API design standards and conventions for United Technologies.
26 Rules
error 13
warn 10
info 3
Rule Categories
get
info
microcks
openapi
operation
parameter
paths
post
response
schema
security
servers
Rules
error
info-title-required
API title must be present.
$.info.title
warn
info-title-collins-prefix
Collins Aerospace API titles should start with "Collins Aerospace".
$.info.title
warn
info-description-required
API description must be present and meaningful.
$.info.description
error
info-version-required
API version must be specified.
$.info.version
warn
openapi-version
APIs should use OpenAPI 3.x.
$.openapi
error
servers-required
Servers array must be defined.
$.servers
error
servers-https-only
All server URLs must use HTTPS.
$.servers[*].url
warn
servers-collins-domain
Collins Aerospace API servers should use collinsaerospace.com domain.
$.servers[*].url
warn
paths-kebab-case
Path segments should use kebab-case.
$.paths[*]~
error
paths-no-trailing-slash
Paths must not end with a trailing slash.
$.paths[*]~
error
operation-summary-required
Every operation must have a summary.
$.paths[*][get,post,put,delete,patch]
info
operation-summary-prefix
Operation summaries should start with Collins Aerospace ARINC.
$.paths[*][get,post,put,delete,patch].summary
warn
operation-description-required
Every operation must have a description.
$.paths[*][get,post,put,delete,patch]
error
operation-id-required
Every operation must have an operationId.
$.paths[*][get,post,put,delete,patch]
warn
operation-id-camel-case
OperationIds should use camelCase.
$.paths[*][get,post,put,delete,patch].operationId
error
operation-tags-required
Every operation must have at least one tag.
$.paths[*][get,post,put,delete,patch].tags
warn
parameter-description-required
Every parameter must have a description.
$.paths[*][get,post,put,delete,patch].parameters[*]
error
parameter-schema-required
Every parameter must have a schema.
$.paths[*][get,post,put,delete,patch].parameters[*]
error
response-success-required
Every operation must define at least one 2xx response.
$.paths[*][get,post,put,delete,patch].responses
warn
response-401-required
All operations should define a 401 Unauthorized response.
$.paths[*][get,post,put,delete,patch].responses
error
response-description-required
Every response must have a description.
$.paths[*][get,post,put,delete,patch].responses[*]
warn
schema-description-required
Top-level schemas should have a description.
$.components.schemas[*]
error
security-schemes-defined
Security schemes must be defined in components.
$.components.securitySchemes
error
get-no-request-body
GET operations must not have a request body.
$.paths[*].get.requestBody
info
post-created-response
POST operations that create resources should return 201 Created.
$.paths[*].post.responses
info
microcks-operation-present
Operations should include x-microcks-operation for mock compatibility.
$.paths[*][get,post,put,delete,patch]