mailboxlayer · API Governance Rules
mailboxlayer API Rules
Spectral linting rules defining API design standards and conventions for mailboxlayer.
11 Rules
error 6
warn 4
info 1
Rule Categories
mailboxlayer
Rules
error
mailboxlayer-operation-summary-required
Every operation must have a summary.
$.paths[*][get,post,put,delete,patch]
warn
mailboxlayer-operation-summary-title-case
Operation summaries should use Title Case (each major word capitalized).
$.paths[*][get,post,put,delete,patch].summary
error
mailboxlayer-operation-id-required
Every operation must define operationId.
$.paths[*][get,post,put,delete,patch]
error
mailboxlayer-operation-tags-required
Every operation must have at least one tag.
$.paths[*][get,post,put,delete,patch]
error
mailboxlayer-access-key-required
Every operation must accept the `access_key` query parameter for authentication.
$.paths[*][get,post,put,delete,patch]
warn
mailboxlayer-server-host
Servers should use the canonical apilayer.net host.
$.servers[*].url
error
mailboxlayer-success-response-defined
Every operation must define a 200 response.
$.paths[*][get,post,put,delete,patch].responses
warn
mailboxlayer-response-content-json
Responses should be returned as application/json.
$.paths[*][get,post,put,delete,patch].responses[*].content
warn
mailboxlayer-info-contact-email
API info must include a support contact email.
$.info.contact
info
mailboxlayer-info-terms-of-service
API info should reference terms of service.
$.info
error
mailboxlayer-security-scheme-apikey
Security schemes must include an API key in the query string named `access_key`.
$.components.securitySchemes[*]