Skip to content

Webhook management

Webhooks allow Batida to integrate with external systems by sending or receiving HTTP requests. Batida supports both inbound webhooks (receiving events from external systems) and outbound webhooks (sending Batida events to external endpoints).

Inbound webhooks

Batida receives external events through the Alert Webhooks endpoint. Monitoring tools like Datadog and Grafana send alerts to:

text
POST /api/v1/webhooks/alerts
Authorization: Bearer <token>

See Alert Webhooks for full setup instructions, supported sources, and field mappings.

Outbound webhooks

Outbound webhooks send Batida events to external systems when specific actions occur.

Creating an outbound webhook

  1. Navigate to Settings > Webhooks.
  2. Click Create Outbound Webhook.
  3. Enter a name, target URL, and the events you want to subscribe to.
  4. Configure retry settings.
  5. Save the webhook.

Supported events

EventDescription
incidents.openedA new incident was created
incidents.status_changedAn incident's status was updated
incidents.resolvedAn incident was resolved

Payload format

Outbound webhooks send a JSON payload with event details:

json
{
  "event": "incidents.opened",
  "timestamp": "2026-04-20T14:30:00Z",
  "data": {
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "title": "Payment gateway returning 500 errors",
    "severity": "SEV2",
    "status": "investigating"
  }
}

Delivery logs

Every webhook delivery is logged. View delivery logs to see:

  • Whether the delivery succeeded or failed.
  • The HTTP status code returned by the target.
  • The request payload and response body.
  • Timestamp of each delivery attempt.

Retry policy

Failed outbound webhook deliveries are retried automatically:

AttemptDelay
1stImmediate
2nd1 minute
3rd5 minutes
4th30 minutes
5th2 hours

If all retries fail, the delivery is marked as failed and logged. You can manually retry from the delivery log.

TIP

Always verify webhook signatures on the receiving end to ensure the payload is authentic. See the API documentation for signature verification details.

Built by the Batida team