Webhooks
thibit sends outgoing webhooks to your backend when workflow events occur, such as a status transition, review requirement, approval, or rejection.
Configure a webhook URL
Webhook subscriptions are configured through the customer external API. The public reference includes the subscription endpoint shape.
Signing
Outgoing webhooks are HMAC-signed. Round 2 will publish the exact canonical string and header names after the sandbox flow is finalized.
Recommended receiver behavior
- Verify the signature before trusting the payload.
- Return a 2xx response only after safely persisting the event.
- Make handlers idempotent; webhook delivery can be retried.
- Fetch the workflow run from the API before activating a high-value user if your business rules require fresh state.