Sysco · API Governance Rules
Sysco API Rules
Spectral linting rules defining API design standards and conventions for Sysco.
13 Rules
error 6
warn 6
info 1
Rule Categories
delivery
list
operation
order
paths
post
product
response
Rules
error
operation-operationId
All operations must have an operationId.
$.paths[*][get,post,put,patch,delete]
error
operation-summary
All operations must have a summary.
$.paths[*][get,post,put,patch,delete]
warn
operation-summary-title-case
Operation summaries must use Title Case.
$.paths[*][get,post,put,patch,delete].summary
warn
operation-tags
All operations must have at least one tag.
$.paths[*][get,post,put,patch,delete]
warn
operation-description
All operations should have a description.
$.paths[*][get,post,put,patch,delete]
error
product-supc-field
Product schema must include a productId (SUPC) field.
$.components.schemas.Product.properties
error
order-delivery-date
Order schema must include a deliveryDate field.
$.components.schemas.Order.properties
error
order-item-quantity
OrderItem schema must include a quantity field.
$.components.schemas.OrderItem.properties
warn
list-pagination-page
List operations should support page parameter for pagination.
$.paths[*].get
info
response-schema-ref
Response schemas should use $ref for maintainability.
$.paths[*][*].responses['200'].content['application/json'].schema
error
post-request-body
POST operations must include a request body.
$.paths[*].post
warn
paths-kebab-case
Path segments must use kebab-case (lowercase with hyphens).
$.paths
warn
delivery-eta-field
Delivery schema should include estimatedArrival for tracking.
$.components.schemas.Delivery.properties