United Airlines · API Governance Rules
United Airlines API Rules
Spectral linting rules defining API design standards and conventions for United Airlines.
15 Rules
error 4
warn 9
info 2
Rule Categories
info
operation
parameter
path
response
schema
servers
ua
Rules
error
operation-operationId
Every operation must have a unique operationId.
$.paths.*[get,post,put,patch,delete,options,head]
warn
operation-summary-title-case
Operation summaries must use Title Case.
$.paths.*[get,post,put,patch,delete].summary
warn
operation-tags
Every operation must include at least one tag.
$.paths.*[get,post,put,patch,delete]
warn
operation-description
Every operation must have a description.
$.paths.*[get,post,put,patch,delete]
warn
path-kebab-case
Path segments must use kebab-case (lowercase with hyphens).
$.paths[*]~
error
path-no-trailing-slash
Paths must not end with a trailing slash.
$.paths[*]~
warn
response-descriptions
All response status codes must include a description.
$.paths.*[get,post,put,patch,delete].responses.*
warn
operation-security-defined
Every operation must define a security requirement.
$.paths.*[get,post,put,patch,delete]
warn
operation-request-body-required
POST, PUT, and PATCH operations should have a requestBody.
$.paths.*[post,put,patch]
warn
info-contact
API info must include contact information.
$.info
info
schema-description
All named schemas should have a description.
$.components.schemas.*
error
operation-success-response
Operations must define at least one 2xx success response.
$.paths.*[get,post,put,patch,delete].responses
warn
parameter-description
All parameters must have a description.
$.paths.*[get,post,put,patch,delete].parameters.*
info
ua-flight-number-format
Flight number examples should follow United Airlines UA format (e.g., UA123).
$.components.schemas.FlightSegment.properties.flightNumber.example
error
servers-defined
API must define at least one server.
$