Webhooks
Register HTTPS callbacks for payment and funding events. Delivery is signed, SSRF-safe, retried via an outbox, and verifiable with the secret returned on create.
Same flow in MCP: rill_webhooks
Auth
Owner Supabase JWT required. Send Idempotency-Key on create. Save the signing secret from the create response, it is required to verify X-Rill-Signature on every delivery.
Authorization: Bearer <owner JWT>Featured endpoints
Register a webhook
POST /webhooksRegister a callback URL for events such as payment.succeeded and funding.paid. Localhost callbacks are allowed outside production. List registered endpoints with GET /webhooks.
Request body
What to save
Save the webhook id and signing secret. Verify X-Rill-Signature (v1,<hmac>), X-Rill-Timestamp (300s tolerance), and X-Rill-Webhook-Id on every delivery.
- Catalog events with GET /webhooks/events.
- Test with POST /webhooks/:id/test; retry with …/deliveries/:deliveryId/retry.
- MCP twin: rill_webhooks action=create|list|test|delete.
All endpoints
Signing and events
- Headers: X-Rill-Signature (v1,<hmac>), X-Rill-Timestamp (300s tolerance), X-Rill-Webhook-Id. Verify with the secret returned on create.
- Events include payment.succeeded, payment.failed, transfer.received, funding.paid, withdrawal.paid, withdrawal.failed, vw.revoked, allowance.reset, seller.withdrawn, resource.updated.