Constant Contact · API Governance Rules
Constant Contact API Rules
Spectral linting rules defining API design standards and conventions for Constant Contact.
9 Rules
error 3
warn 5
info 1
Rule Categories
constant
Rules
error
constant-contact-info-contact
API contact information must be present.
$.info
warn
constant-contact-host
Host (Swagger 2.0) or server URL (OAS 3.x) must point to api.cc.email.
$.host$.servers[*].url
warn
constant-contact-base-path
Base path must be /v3.
$.basePath
error
constant-contact-oauth2
An OAuth2 security definition must be present.
$.securityDefinitions[*]$.components.securitySchemes[*]
error
constant-contact-operation-id
Every operation must declare a unique operationId.
$.paths[*][get,post,put,patch,delete]
warn
constant-contact-operation-tags
Operations must declare at least one tag.
$.paths[*][get,post,put,patch,delete]
warn
constant-contact-json-content
Operations should accept and return application/json.
$.paths[*][post,put,patch]
warn
constant-contact-error-responses
Mutating operations should declare 4xx error responses.
$.paths[*][post,put,patch,delete].responses
info
constant-contact-cursor-pagination
Collection GETs should expose a `cursor` or `limit` query parameter.
$.paths[?(@property.match(/(contacts|contact_lists|contact_tags|emails|events|segments)$/))].get