How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Honeycomb Anomaly Detection API

The Anomaly Detection API exposes Honeycomb Signals - the anomaly detection profiles Honeycomb maintains per service - and their historical anomalies. List and retrieve Signals, update a Signal's configuration and recipients, and read the historical anomalies a Signal has recorded. Requires anomaly detection to be enabled for the team.

Honeycomb Anomaly Detection API is one of 22 APIs that Honeycomb publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Anomaly Detection. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 4 operations across 3 paths, and defines 19 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://api.honeycomb.io, https://api.eu1.honeycomb.io.

4 operations 3 paths 19 schemas 3 GET1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.honeycomb.io
Authentication
API Key
License
Resource Areas
1

Authentication & Security 1

Honeycomb Anomaly Detection API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-Honeycomb-Team (configuration_key).

  • configuration_key — Authenticate using a Honeycomb Configuration Key. Pass the Token in the X-Honeycomb-Team header: http X-Honeycomb-Team: 1234567890123456789012 If you created y…

Paths & Operations 4

Across 3 paths, the API surfaces 4 operations — 3 GET, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Anomaly Detection 4

Anomaly Detection is in public beta. Endpoints and response shapes may change. Anomaly Detection identifies Signals - patterns in your services that deviate from their historical…

GET
/1/signals
List All Signals
listSignals 7 params → 200401403404422429default
GET
/1/signals/{id}
Get a Signal
getSignal 1 param → 200401403404429default
PUT
/1/signals/{id}
Update a Signal
updateSignal 1 param body → 200400401403404409422429
GET
/1/signals/{id}/historical_anomalies
List Historical Anomalies
listSignalHistoricalAnomalies 5 params → 200400401403404422429default

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are Signal (14 properties), DetailedError (6 properties), HistoricalAnomaly (5 properties), NotificationRecipient (4 properties). Each schema is shown below with its type and property counts.

PaginationLinks
object
Links to iterate through the pages of results.
1 property 1 required
Error
object
A legacy error, containing only a textual description.
1 property
AnomalySignal
string
The kind of measurement the Signal is trained on. - errorrate: The fraction of erroring requests for the service. - presence: Whether the service is producing…
PaginatedSignalsResponse
object
A page of Signals.
2 properties 1 required
NotificationRecipientDetails
object
3 properties
JSONAPIError
object
A JSONAPI-formatted error message.
1 property
UpdateSignalRequest
object
Fields to update on a Signal. All fields are optional and only supplied fields are applied.
3 properties
NotificationRecipient
object
4 properties
SignalRecipient
object
A Recipient assigned to a Signal.
2 properties 1 required
DetailedError
object
An RFC7807 'Problem Detail' formatted error message.
6 properties 4 required
HistoricalAnomalyNormalRange
object
The trained normal band a measurement exceeded.
2 properties 2 required
SignalDetailResponse
A Signal with its assigned Recipients.
ValidationError
HistoricalAnomaly
object
A resolved anomaly that a Signal previously fired for.
5 properties 5 required
RecipientType
string
One of the supported Recipient Types
Signal
object
A Honeycomb Anomaly Detection Signal.
14 properties 14 required
AnomalySignalStatus
string
The lifecycle status of the Signal. ineligible is returned when the underlying service does not meet the conditions required for training.
PaginatedHistoricalAnomaliesResponse
object
A page of resolved historical anomalies for a Signal.
2 properties 1 required
AnomalySignalSensitivity
string
How far a measurement must deviate from the trained normal band before the Signal fires. Higher sensitivity narrows the normal band and catches smaller deviati…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

honeycomb-io-anomaly-detection-api-openapi.yml Raw ↑

Other APIs Honeycomb publishes across the network.

Honeycomb Auth API
Honeycomb Boards API
Honeycomb Burn Alerts API
Honeycomb Calculated Fields API
Honeycomb Columns API
Honeycomb Dataset Definitions API
Honeycomb Datasets API
Honeycomb Environments API
Honeycomb Events API
Honeycomb Key Management API
Honeycomb Kinesis Events API
Honeycomb Marker Settings API
Where this information came from

This is an independent, third-party profile of Honeycomb Anomaly Detection API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.