Honeycomb · API Governance Rules

Honeycomb API Rules

Spectral linting rules defining API design standards and conventions for Honeycomb.

10 Rules error 3 warn 6
View Rules File View on GitHub

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]+\}/)]

Spectral Ruleset

Raw ↑
extends:
  - spectral:oas
  - spectral:asyncapi

functionsDir: ./functions
functions: []

rules:
  # --- Honeycomb naming and structural conventions ---

  honeycomb-paths-snake-case:
    description: Honeycomb paths and path segments use snake_case (e.g. /1/dataset_definitions, /1/burn_alerts).
    severity: warn
    given: $.paths[*]~
    then:
      function: pattern
      functionOptions:
        match: '^/[0-9]+(/[a-z][a-z0-9_]*|/\{[A-Za-z]+\})+/?$'

  honeycomb-versioned-base-path:
    description: Honeycomb APIs are versioned at the path root; every path MUST start with /1/ or /2/.
    severity: error
    given: $.paths[*]~
    then:
      function: pattern
      functionOptions:
        match: '^/[12]/'

  honeycomb-v2-uses-jsonapi:
    description: v2 endpoints (under /2/teams/...) return application/vnd.api+json per JSON:API spec.
    severity: warn
    given: $.paths[?(@property =~ /^\/2\//)][*].responses[?(@property =~ /^2/)].content
    then:
      field: application/vnd.api+json
      function: truthy

  honeycomb-operation-tag-required:
    description: Every Honeycomb operation MUST be tagged for navigation in the interactive docs.
    severity: error
    given: $.paths[*][get,post,put,patch,delete].tags
    then:
      function: length
      functionOptions:
        min: 1

  honeycomb-summary-title-case:
    description: Operation summaries are written in Title Case (e.g. "Create A Marker", "List All SLOs").
    severity: warn
    given: $.paths[*][get,post,put,patch,delete].summary
    then:
      function: pattern
      functionOptions:
        match: '^[A-Z][A-Za-z0-9 ]+$'

  honeycomb-camel-case-properties:
    description: Honeycomb v1 response properties use snake_case at the wire level (id, last_written_at,
      created_at).
    severity: warn
    given: $.components.schemas[*].properties[*]~
    then:
      function: pattern
      functionOptions:
        match: '^[a-z][a-z0-9_]*$'

  honeycomb-securityscheme-defined:
    description: Honeycomb requires an X-Honeycomb-Team apiKey security scheme.
    severity: error
    given: $.components.securitySchemes
    then:
      field: configuration_key
      function: truthy

  honeycomb-error-response-has-error-property:
    description: 4xx and 5xx responses MUST surface an `error` property describing the failure.
    severity: warn
    given: $.paths[*][get,post,put,patch,delete].responses[?(@property =~ /^[45]/)].content.*.schema.properties
    then:
      field: error
      function: truthy

  honeycomb-list-endpoints-paginated-or-bounded:
    description: List endpoints SHOULD describe pagination or boundedness in their summary or description.
    severity: hint
    given: $.paths[?(@property =~ /^\/1\/[a-z_]+$/)].get
    then:
      field: description
      function: truthy

  honeycomb-dataset-slug-path-param:
    description: Per-dataset endpoints use {datasetSlug} as the path parameter name.
    severity: warn
    given: $.paths[?(@property =~ /\/[0-9]+\/[a-z_]+\/\{[A-Za-z]+\}/)]
    then:
      function: truthy

Work with this as data

Every ruleset here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for spectral rules

4 MCP tools reach this
  • find_rulesBrowse and filter every ruleset in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This ruleset
curl "https://apis.io/api/v1/rules/honeycomb-rules"
All spectral rules
curl "https://apis.io/api/v1/rules?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.