This glossary explains what each Collection Partner webhook event means in business terms - when it fires and what it signals about a case assigned to your agency. For payload schemas, signature verification, and endpoint setup, see Developer Docs.
Event overview
Debitura sends collection partners seven webhook event types, covering case lifecycle, payments, and chat.
Event | Category | What it signals |
case.assigned | Case lifecycle | A case was assigned to your agency |
case.updated | Case lifecycle | An assigned case changed lifecycle state |
case.closed | Case lifecycle | An assigned case was closed |
case.declined | Case lifecycle | An auto-assigned case was declined by an Exclusive partner |
payment.created | Payments | A payment was registered on an assigned case |
payment.deleted | Payments | A previously-recorded payment on an assigned case was removed |
chat.created | Communication | A new chat message was posted on an assigned case |
Case lifecycle events
These events track a case from the moment it reaches your agency through to closure. Each payload identifies the case by its reference number.
case.assigned
When it fires: A case has been validated by Debitura and assigned to your agency. This is the entry point for your involvement with the case.
What it means: A new case is now yours to work. You receive case.assigned rather than case.created because the creditor created the case; assignment happens only after Debitura validates and routes it, which can be hours or days later.
What to do: Record the case in your system using its reference, review the details, and begin work. The payload includes the case reference and the current lifecycle state (typically Active).
case.updated
When it fires: An assigned case changes lifecycle state.
What it means: The case has moved forward or backward in its lifecycle. The payload includes both the previous and the new state.
What to do: Update the case status in your system to match the new state. See Case lifecycle (deep dive) for what each state means.
case.closed
When it fires: An assigned case is closed.
What it means: Collection activity on the case has ended. The payload's closeCode indicates the outcome (for example, Paid).
What to do: Mark the case as closed in your system. The closeCode uses the same set as the platform close codes - see Case close codes.
case.declined
When it fires: An assigned case is declined by your agency. This event applies only to Exclusive partners declining an auto-assigned case. Legal Network partners who choose not to quote on a lead use a separate lead flow and never receive this event.
What it means: You rejected the case. It is removed from your queue and released to the partner network as an open lead for other eligible partners to quote on - it is not automatically reassigned to one specific partner.
What to do: Remove the case from your active work queue if you had already recorded it as assigned.
Payment events
payment.created
When it fires: A payment is registered on a case assigned to you.
What it means: Money has been recorded against the debt.
What to do: Reconcile the payment in your own system and update the outstanding balance for the case.
payment.deleted
When it fires: A previously-recorded payment on one of your assigned cases is removed (for example, entered in error).
What it means: The payment recorded earlier no longer stands.
What to do: Reconcile - reduce or reverse the corresponding entry in your own system.
Communication events
chat.created
When it fires: A new chat message is created on a case assigned to you.
What it means: There is a new message in the case communication thread.
What to do: Read the message and respond in the case chat where needed, so the conversation stays on record.
Managing your subscription
You subscribe by registering an HTTPS endpoint together with the list of event types you want to receive. A test mode option lets you receive events from test cases only while you build and validate your integration, before switching to live production events.
Debitura automatically retries failed deliveries, and an endpoint that keeps failing is disabled until you fix it and re-enable it. For the exact setup, payload schemas, signature verification, retry and re-enable behaviour, and the endpoint reference, see Developer Docs.
Developer Docs: Developers: for endpoint setup, payload schemas, and signature verification, see Developer Docs: Webhooks and the Collection Partner API reference.