The webhook delivery channel. All Rollbar webhook events are sent as HTTP POST requests to the configured URL. Rules can override the destination URL on a per-rule basis.
Triggered when an error or message is seen for the first time.
Content-Type: application/json
occurrence
Triggered on every occurrence of an error or message.
Content-Type: application/json
exp_repeat_item
Triggered on the 10th, 100th, 1000th, and subsequent exponential occurrences of an item.
Content-Type: application/json
item_velocity
Triggered when an item's occurrence rate exceeds a configured threshold.
Content-Type: application/json
resolved_item
Triggered when an item is marked as resolved.
Content-Type: application/json
reactivated_item
Triggered when a resolved item occurs again, changing its status back to active.
Content-Type: application/json
reopened_item
Triggered when a resolved or muted item is manually reopened.
Content-Type: application/json
deploy
Triggered when a deployment is reported to Rollbar.
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.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
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.