Assembled · API Governance Rules
Assembled API Rules
Spectral linting rules defining API design standards and conventions for Assembled.
8 Rules
error 3
warn 4
Rule Categories
assembled
Rules
error
assembled-info-contact-required
All Assembled OpenAPI specs must declare a support contact.
$.info
warn
assembled-operation-summary-title-case
Operation summaries must start with "Assembled " and use Title Case.
$.paths.*[get,post,put,patch,delete].summary
warn
assembled-operation-id-camel-case
operationId must be camelCase (no underscores, no hyphens).
$.paths.*[get,post,put,patch,delete].operationId
warn
assembled-path-snake-case
Path segments must use lower snake_case (per Assembled API style).
$.paths
warn
assembled-server-versioned-base
Servers should target the documented production base URL.
$.servers[*].url
error
assembled-basic-auth-required
Each spec must declare HTTP Basic Auth.
$.components.securitySchemes
error
assembled-tag-defined
Operations must declare at least one tag.
$.paths.*[get,post,put,patch,delete].tags
hint
assembled-error-response-defined
Operations that can be rate-limited (all v0) should document a 429 response.
$.paths.*[get,post,put,patch,delete].responses