Webhooks push ICP events to your systems as they happen — so a new or escalated ticket can open a chat message, update a dashboard, or drive a workflow without polling. Outbound webhooks for ticket and device events ship with the platform alongside its REST API.
Subscribe
An admin registers an endpoint (a URL) and the events it should receive:
| Event | Fires when |
|---|---|
ticket.opened | A ticket is created |
alert.ticket | An alert opened a ticket |
ticket.escalated | A ticket is escalated |
ticket.re-escalated | An escalated ticket escalates again |
command.failed | A device command failed |
* | Subscribe to all events |
Verify deliveries
Each endpoint gets a signing secret, generated once, so you can verify that a delivery really came from ICP. The endpoint list masks the secret after creation.
Manage endpoints
- Enable / disable an endpoint
- Test-deliver on demand to check your receiver
- See last-delivery status and a failure count
Warning
Always verify the signature on an incoming webhook before acting on it, and respond quickly (do heavy work asynchronously). Endpoints that keep failing are surfaced by their failure count so you can fix or disable them.