Skip to main content
The FloKit v1 REST API is in design-partner preview — endpoints and schemas may change before general availability. Contact your FloKit team for access.
FloKit sends webhook payloads to your configured endpoint when key events occur — actions created, approved, or rolled back; guardrails triggered; payback reports updated; or integrations failing to sync.

Setup

Go to FloKit → Settings → Webhooks → Add endpoint. Enter your HTTPS URL and select the event types you want to subscribe to.

Webhook events


Payload format

All payloads follow the same envelope structure.

Signature verification

FloKit signs every webhook request with HMAC-SHA256. Verify the signature before processing the payload. Header: FloKit-Signature: sha256=<hex_digest> The signing secret is available in FloKit → Settings → Webhooks → your endpoint → Signing secret.
Use the raw request body (before JSON parsing) when computing the HMAC. JSON serialization differences will cause signature mismatches.

Retries

FloKit retries failed webhook deliveries — any response that is not a 2xx status — up to 5 times with exponential backoff: After 5 consecutive failures, the endpoint is temporarily disabled and an integration.error event fires to your other active endpoints. Re-enable the endpoint in FloKit → Settings → Webhooks. To avoid retries, return 200 OK immediately and process the payload asynchronously.

POST /v1/webhooks/test

Send a sample payload to your configured endpoint to verify your integration.

Request body

string
required
The webhook event type to simulate. FloKit sends a realistic sample payload for the specified event to your configured endpoint.

Response

Use the delivery_id to look up delivery logs in FloKit → Settings → Webhooks → your endpoint → Delivery history.