ATTOM · API Governance Rules
ATTOM API Rules
Spectral linting rules defining API design standards and conventions for ATTOM.
10 Rules
error 6
warn 3
info 1
Rule Categories
attom
Rules
error
attom-operation-id-pattern
ATTOM operationIds must be lowerCamelCase verb-resource ("getPropertyDetail", "searchPois").
$.paths.*[get,post,put,patch,delete].operationId
error
attom-operation-summary-title-case
Operation summaries must use Title Case ("Get Property Detail", not "Get property detail").
$.paths.*[get,post,put,patch,delete].summary
error
attom-operation-tag-required
Every operation must have at least one tag.
$.paths.*[get,post,put,patch,delete]
error
attom-path-no-trailing-slash
Paths must not end with a trailing slash (except the root).
$.paths
warn
attom-path-kebab-or-flat
ATTOM paths use flat-case or single-word segments (no camelCase except v4 endpoints).
$.paths
error
attom-security-apikey-header
ATTOM APIs MUST authenticate via the `apikey` header.
$.components.securitySchemes
error
attom-global-security-required
Specs must declare a top-level security requirement.
$
warn
attom-server-base-url
ATTOM servers should point at api.gateway.attomdata.com.
$.servers[*].url
info
attom-status-envelope
Every 200 response schema should reference a status block.
$.components.schemas
warn