Walgreens · API Governance Rules
Walgreens API Rules
Spectral linting rules defining API design standards and conventions for Walgreens.
10 Rules
error 4
warn 6
Rule Categories
walgreens
Rules
error
walgreens-api-key-required
All Walgreens API requests must include apiKey in the request body
$.paths[*][post,patch,put].requestBody.content.application/json.schema.required
error
walgreens-affiliate-id-required
All Walgreens API requests must include affId in the request body
$.paths[*][post,patch,put].requestBody.content.application/json.schema.required
warn
walgreens-base-url-consistency
All Walgreens API servers must use services.walgreens.com for production
$.servers[*].url
error
walgreens-operation-ids
All Walgreens API operations must have operationId
$.paths[*][get,post,put,patch,delete]
warn
walgreens-operation-summaries
All Walgreens API operations must have a summary
$.paths[*][get,post,put,patch,delete]
warn
walgreens-request-content-type
POST and PATCH operations must specify application/json content type
$.paths[*][post,patch].requestBody.content
warn
walgreens-versioned-paths
API paths should include a version segment
$.paths
error
walgreens-https-only
All Walgreens API server URLs must use HTTPS
$.servers[*].url
warn
walgreens-error-responses
All Walgreens API operations should document error responses
$.paths[*][post,patch,put,get].responses
warn
walgreens-response-schema
Successful responses should have a schema defined
$.paths[*][get,post,put,patch].responses[200,201].content.application/json