Status updates. Via webhook.

How it works

You provide an HTTPS endpoint. When an incident occurs, Fluxa sends a JSON POST to your endpoint signed with HMAC-SHA256 (the same signature scheme as transaction webhooks). Your endpoint validates the signature, processes the payload, and returns a 2xx response.

Delivery semantics:

• At-least-once · if your endpoint returns non-2xx or times out, Fluxa retries with exponential backoff: 1s, 5s, 30s, 5m, 1h, 6h, 24h
• Idempotency key · every delivery carries an X-Fluxa-Delivery-Id header; replays of the same incident update share the same delivery ID so you can deduplicate
• Signature verification · X-Fluxa-Signature header contains the HMAC-SHA256 of the request body; verify against your shared secret before processing
• Versioned payload · version field in every payload; breaking changes go to a new version with sixty days’ notice

Payload format

Example incident payload:

POST https://your-endpoint.co.uk/fluxa-status
Content-Type: application/json
X-Fluxa-Signature: sha256=...
X-Fluxa-Delivery-Id: dlv_01H...
X-Fluxa-Event: incident.created

{
  "version": "2026-05-01",
  "event": "incident.created",
  "incident": {
    "id": "INC-2026-0001",
    "severity": "SEV-2",
    "status": "investigating",
    "title": "Elevated error rates on POST /v1/payments",
    "components": ["api"],
    "created_at": "2026-05-15T14:23:11Z",
    "updated_at": "2026-05-15T14:23:11Z",
    "url": "https://fluxapay.co.uk/live"
  }
}

Event types: incident.created, incident.updated, incident.resolved, maintenance.scheduled, maintenance.in_progress, maintenance.completed.

Subscribe