Ironclad · API Governance Rules
Ironclad API Rules
Spectral linting rules defining API design standards and conventions for Ironclad.
8 Rules
error 1
warn 6
info 1
Rule Categories
ironclad
Rules
warn
ironclad-info-version-numeric
Ironclad uses a single integer (1) as the API version on every public spec.
$.info.version
warn
ironclad-server-includes-region
Every Ironclad server URL must encode a region (na1, eu1, or demo).
$.servers[*].url
warn
ironclad-operation-id-camelcase
Ironclad operationIds are camelCase.
$.paths[*][get,post,put,patch,delete].operationId
warn
ironclad-operation-summary-title-case
Operation summaries should be Title Case (e.g., "List All Workflows", not "list all workflows").
$.paths[*][get,post,put,patch,delete].summary
error
ironclad-tag-defined
Every operation must be tagged with at least one of the canonical resource tags.
$.paths[*][get,post,put,patch,delete]
info
ironclad-pagination-cursor-param
List endpoints should expose cursor-based pagination via a 'nextPageToken' or 'cursor' query parameter.
$.paths[?(@.get && @.get.operationId =~ /list.*/i)].get.parameters[*].name
warn
ironclad-error-schema-defined
4xx and 5xx responses should reference a shared error schema.
$.paths[*][get,post,put,patch,delete].responses['400','401','403','404','409','422','429','500']
warn
ironclad-oauth-bearer-security
Public API operations should declare the OAuth bearer security scheme.
$.paths[*][get,post,put,patch,delete]