Webhooks Overview
Receive signed HTTP POST events when incidents fire, get acknowledged, or resolve, instead of polling the Trasys Public API for incident state changes.
Webhooks let Trasys push events to your own HTTP endpoint instead of you polling the API. When something happens — an alert fires, an incident is acknowledged, an anomaly is detected — Trasys sends a signed POST request to every registered endpoint that subscribed to that event.
How it works
- You register an endpoint URL in the Webhooks page of your project dashboard.
- Trasys verifies the URL responds with
2xxbefore saving it. - A webhook secret is generated and shown once — store it securely.
- On each matching event, Trasys sends a HMAC-signed POST to your endpoint.
- If delivery fails, a retry is attempted after 60 seconds (backed by a persistent DB queue — survives server restarts).
Event flow
Alert rule fires
→ incident.created ──► your endpoint
→ alert.fired ──► your endpoint
User acknowledges incident
→ incident.updated ──► your endpoint
Incident resolved
→ incident.resolved ──► your endpointExplore
Setup
Create and manage webhook endpoints.
Event types
All events and their payload schemas.
Security
Verify incoming requests with HMAC.
Delivery logs
View delivery history and retry behaviour.
Webhook events are fire-and-forget from Trasys's perspective. Your endpoint must respond within 10 seconds or the attempt is counted as failed and scheduled for retry.
Pulse
Pulse runs scheduled HTTP checks against your endpoints from outside and alerts you when they fail, covering monitor types, assertions, and multi-step flows.
Setup
Create a webhook endpoint, pass URL verification, subscribe to the events you need, and securely store the one-time secret used to sign every delivery.