Webhook Deliveries
Configure outbound webhooks and troubleshoot delivery attempts.
Keymint sends signed HTTPS requests to enabled endpoints when subscribed events occur. Configure endpoints under Developer → Webhooks.
Deliveries versus events
The Deliveries tab contains only attempted outbound requests. Each row shows the endpoint, event type, delivery status, HTTP response, attempt count, and timestamp. Internal events that did not match an endpoint are not deliveries.
The endpoint view is useful for configuration and health. Open a delivery to inspect its response and payload metadata. Do not treat an internal event as proof that your endpoint received a request.
Delivery status
Successful 2xx responses are marked delivered. Timeouts, connection errors, and non-2xx responses are retried with exponential backoff, up to five attempts. A failed row can be retried manually from the delivery details view.
Your handler should acknowledge quickly, process asynchronously, and be idempotent using Keymint-Event-Id or Keymint-Delivery-Id.
Verify signatures
Verify the Keymint-Signature header against the raw request body before processing. See Webhooks & Events for the signing algorithm, replay protection, headers, and example verification code.
Troubleshooting
- No delivery exists: the endpoint was disabled or was not subscribed to that event.
- Repeated failures: inspect the HTTP response and endpoint availability, then retry after fixing the handler.
- Signature failures: use the endpoint’s current secret and the unmodified raw body.
- Duplicate processing: deduplicate by event ID; retries represent the same event, not a new business action.