Honeycomb · API Governance Rules
Honeycomb API Rules
Spectral linting rules defining API design standards and conventions for Honeycomb.
10 Rules
error 3
warn 6
Rule Categories
honeycomb
Rules
warn
honeycomb-paths-snake-case
Honeycomb paths and path segments use snake_case (e.g. /1/dataset_definitions, /1/burn_alerts).
$.paths[*]~
error
honeycomb-versioned-base-path
Honeycomb APIs are versioned at the path root; every path MUST start with /1/ or /2/.
$.paths[*]~
warn
honeycomb-v2-uses-jsonapi
v2 endpoints (under /2/teams/...) return application/vnd.api+json per JSON:API spec.
$.paths[?(@property =~ /^\/2\//)][*].responses[?(@property =~ /^2/)].content
error
honeycomb-operation-tag-required
Every Honeycomb operation MUST be tagged for navigation in the interactive docs.
$.paths[*][get,post,put,patch,delete].tags
warn
honeycomb-summary-title-case
Operation summaries are written in Title Case (e.g. "Create A Marker", "List All SLOs").
$.paths[*][get,post,put,patch,delete].summary
warn
honeycomb-camel-case-properties
Honeycomb v1 response properties use snake_case at the wire level (id, last_written_at, created_at).
$.components.schemas[*].properties[*]~
error
honeycomb-securityscheme-defined
Honeycomb requires an X-Honeycomb-Team apiKey security scheme.
$.components.securitySchemes
warn
honeycomb-error-response-has-error-property
4xx and 5xx responses MUST surface an `error` property describing the failure.
$.paths[*][get,post,put,patch,delete].responses[?(@property =~ /^[45]/)].content.*.schema.properties
hint
honeycomb-list-endpoints-paginated-or-bounded
List endpoints SHOULD describe pagination or boundedness in their summary or description.
$.paths[?(@property =~ /^\/1\/[a-z_]+$/)].get
warn
honeycomb-dataset-slug-path-param
Per-dataset endpoints use {datasetSlug} as the path parameter name.
$.paths[?(@property =~ /\/[0-9]+\/[a-z_]+\/\{[A-Za-z]+\}/)]