Goal
Configure webhook subscriptions in Debitura so your systems receive automatic notifications when events occur on your collection cases.
Prerequisites
An active Debitura client account
An HTTPS endpoint on your server that can receive POST requests (your developer will set this up)
Available webhook events
Customer Webhooks support the following events:
Event | Description |
case.created | A new collection case is created |
case.updated | A case's lifecycle status changes (e.g., from Active to Closed) |
case.closed | A case is closed (paid, written off, or otherwise resolved) |
payment.created | A payment is registered on a case |
chat.created | A chat message is added to a case |
Steps
Go to Webhooks settings
Navigate to Webhooks settings in the Debitura platform.Create a webhook subscription
Enter the endpoint URL your developer has prepared and select which events you want to receive. When you save, Debitura generates a signing secret. Copy this secret immediately and share it securely with your developer - it is shown only once.Share details with your developer
Your developer will need the signing secret to verify that webhook deliveries are genuinely from Debitura. They should implement signature verification and test the endpoint using the test function in the platform.
Result
Once configured, your systems will automatically receive HTTP POST requests when the selected events occur on your cases. This enables real-time synchronization without polling the API.
Technical implementation
Webhook implementation requires developer involvement for endpoint setup, signature verification, and event processing. For complete technical documentation including payload structures, security requirements, and code examples, see the Developer Docs resources below.
Want to implement webhooks? See Developer Docs: Client Webhooks for the client-specific implementation guide, or Developer Docs: Webhooks for general webhook mechanics.