Generic Webhook integration. Honeybadger POSTs a JSON body to the
configured webhook URL whenever an event fires in the project. The
JSON body always contains an `event` string and a human-readable
`message`, plus one or more event-specific objects.
Receive Honeybadger project events on a generic webhook URL.
Messages
occurred
Fired when a new error (fault) is detected in a project.
Content-Type: application/json
resolved
Fired when a fault is marked resolved.
Content-Type: application/json
unresolved
Fired when a previously resolved fault recurs.
Content-Type: application/json
assigned
Fired when a fault is assigned to a user.
Content-Type: application/json
commented
Fired when a comment is added to a fault.
Content-Type: application/json
rate_exceeded
Fired when a fault's error rate threshold is exceeded.
Content-Type: application/json
deployed
Fired when a deployment is recorded against a project.
Content-Type: application/json
check_in_missing
Fired when an expected check-in is absent (a missed cron/heartbeat).
Content-Type: application/json
check_in_reporting
Fired when a previously missing check-in starts reporting again.
Content-Type: application/json
down
Fired when an uptime check fails (site is down).
Content-Type: application/json
up
Fired when an uptime check recovers (site is back up).
Content-Type: application/json
cert_will_expire
Fired when a monitored site's SSL certificate is approaching expiry.
Content-Type: application/json
About AsyncAPI
The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.