AsyncAPI channel · Rollbar
· Rollbar Webhook Events
/webhook
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.
Channel address
/webhook
Operations
publish
receiveWebhookEvent
Receive a Rollbar webhook event
Messages
new_item
Triggered when an error or message is seen for the first time.
Content-Type:
application/jsonoccurrence
Triggered on every occurrence of an error or message.
Content-Type:
application/jsonexp_repeat_item
Triggered on the 10th, 100th, 1000th, and subsequent exponential occurrences of an item.
Content-Type:
application/jsonitem_velocity
Triggered when an item's occurrence rate exceeds a configured threshold.
Content-Type:
application/jsonresolved_item
Triggered when an item is marked as resolved.
Content-Type:
application/jsonreactivated_item
Triggered when a resolved item occurs again, changing its status back to active.
Content-Type:
application/jsonreopened_item
Triggered when a resolved or muted item is manually reopened.
Content-Type:
application/jsondeploy
Triggered when a deployment is reported to Rollbar.
Content-Type:
application/jsonAbout 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.
Browse every event-driven channel on the APIs.io network or compare with the broader Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.