Webhooks Integration
Send TigerOps alerts to any HTTP endpoint with fully configurable JSON payload templates. Build custom alert pipelines, fan out to multiple systems, and integrate with any internal tooling.
How It Works
Register Your Webhook Endpoint
In TigerOps, navigate to Integrations > Webhooks and enter the HTTPS URL of your endpoint. TigerOps will send a test POST request to verify connectivity.
Configure Authentication
Add an optional shared secret for HMAC-SHA256 signature verification, or configure Bearer token or Basic Auth headers for your endpoint security requirements.
Customize the Payload Template
Use TigerOps template variables to shape the JSON payload exactly as your downstream system expects — map any alert field to any JSON key.
Set Event Filters and Retry Policy
Choose which alert events trigger the webhook (create, update, resolve) and configure retry behavior with exponential backoff for failed deliveries.
What You Get Out of the Box
Configurable JSON Payload Templates
Define the exact JSON structure your endpoint expects using template variables like {{severity}}, {{service_name}}, {{ai_summary}}, {{trace_url}}, and {{timestamp}}.
HMAC Signature Verification
Every webhook request includes an X-TigerOps-Signature header with an HMAC-SHA256 signature of the payload, so your endpoint can verify authenticity before processing.
Event Type Filtering
Subscribe to specific event types per webhook: incident.created, incident.updated, incident.resolved, anomaly.detected, or slo.breached — independently per endpoint.
Retry with Exponential Backoff
Failed webhook deliveries are retried up to 10 times over 24 hours with exponential backoff. Delivery status and response codes are visible in the webhook delivery log.
Multiple Endpoints per Policy
Fan out a single TigerOps alert to multiple webhook endpoints simultaneously. Different teams can subscribe to the same alert events via separate endpoints.
Delivery Log and Debugging
The TigerOps webhook delivery log shows every outbound request: URL, timestamp, status code, response body, and retry history — making it easy to debug integration issues.
Webhook Payload Template
Define the JSON structure and event filters for your outbound webhook endpoint.
{
"webhook": {
"url": "https://your-service.internal/tigerops-alerts",
"method": "POST",
"secret": "${WEBHOOK_SHARED_SECRET}",
"auth": {
"type": "bearer",
"token": "${WEBHOOK_BEARER_TOKEN}"
},
"events": [
"incident.created",
"incident.resolved",
"slo.breached"
],
"filters": {
"min_severity": "warning",
"environments": ["production"]
},
"payload_template": {
"id": "{{incident_id}}",
"title": "{{incident_title}}",
"severity": "{{severity}}",
"service": "{{service_name}}",
"summary": "{{ai_summary}}",
"trace_url": "{{trace_url}}",
"started_at": "{{started_at}}",
"resolved_at": "{{resolved_at}}",
"dashboard_url": "{{tigerops_url}}"
},
"retry": {
"max_attempts": 10,
"backoff": "exponential"
}
}
}Common Questions
What HTTP methods and content types does TigerOps use for webhooks?
TigerOps sends HTTP POST requests with a Content-Type of application/json. The payload is always a JSON object. Headers include X-TigerOps-Signature for verification, X-TigerOps-Event for the event type, and X-TigerOps-Delivery for the unique delivery ID.
How do I verify that the webhook is genuinely from TigerOps?
TigerOps signs every payload with HMAC-SHA256 using your shared secret. Compute the HMAC of the raw request body using your secret and compare it to the value in the X-TigerOps-Signature header. Reject requests where signatures do not match.
What happens if my endpoint is down and misses a webhook delivery?
TigerOps retries failed deliveries up to 10 times using exponential backoff — starting at 30 seconds, doubling each attempt, up to a maximum of 24 hours. You can also manually re-deliver any past event from the webhook delivery log.
Can I send different fields for different alert severities?
Yes. TigerOps supports conditional template logic in payload templates. You can include additional fields like runbook_url and pagerduty_escalation only when severity equals critical, while using a simpler payload for warnings.
Is there a rate limit on webhook deliveries?
TigerOps delivers webhooks as events occur with no artificial rate limiting. However, alert deduplication means grouped incidents fire a single webhook rather than one per underlying alert. During burst conditions, deliveries are queued and processed in order.
Connect TigerOps to Any System
No credit card required. Register a webhook in seconds. Custom payload templates immediately.