Automating Case Updates

Send case activity and payments through the API instead of completing the monthly case update in the Partner Portal.

How It Works

By default, Debitura generates a monthly case update request for every active case assigned to you, surfaced in the Partner Portal as an Update Case Status task.

Once your integration is feeding case activity and payments, Debitura switches your partner account to a mode where those monthly requests are no longer generated. You report continuously through the API; the recurring manual task stops.

Default          Debitura → monthly update request → you complete it in the portal

Automated        You → case activity + payments via API → Debitura
                 (no monthly update request generated)

The setting is on your partner account, not per case. It applies to every case assigned to you.

What You Need to Send

Two data types cover what the monthly update collects:

Data	Endpoint	Notes
Payments	POST /cases/{id}/payments	Omit the payout split and Debitura computes it from the case terms. See Record Payments.
Case activity	POST /cases/{id}/notes or POST /ingestion-jobs	Use /ingestion-jobs to batch up to 1,000 rows. See Update Case Progress and Ingestion Jobs.

Both must arrive on a regular cadence, and both must reference cases that resolve — see Case matching below.

Case activity is free text. There is no activity-type field: POST /cases/{id}/notes takes a description and an optional eventDate, and /ingestion-jobs currently accepts only type: 0 (Note). Back-date eventDate so the timeline reflects when the activity actually happened rather than when you posted it.

Case Matching

Every row you send must resolve to a Debitura case. Rows that do not match are not applied.

Resolve case IDs ahead of time using your own reference:

• GET /cases/by-partner-reference/{reference} — single lookup
• GET /cases/by-partner-reference?references= — batch, up to 100
• GET /cases/by-creditor-reference — by the creditor's reference

Set your reference on cases before you start sending data.

Silent under-reporting

Unmatched references are the most common reason an automated feed silently under-reports.

Checking Your Own State

GET /me returns surveyCadenceMode:

Value	Meaning
Standard	Monthly update requests are generated for your cases
DecisionPointOnly	No monthly update requests are generated

The same field appears on the collection partner object embedded in case responses, so you can branch per case without a second call.

What Still Requires the Portal

Automating case updates replaces recurring reporting. It does not replace decisions.

No API endpoint exists for these — handle them in the Partner Portal:

• Pausing a case
• Extending the collection period (promise to pay, payment agreement)
• Registering a debtor dispute
• Legal escalation and legal quotes

Available via the API, though many partners still handle them manually:

• POST /cases/{id}/close — closing a case, with a close code
• POST /cases/{id}/start — accepting and starting a case

The End of the Collection Period

When a case's exclusive collection period approaches its end, the next step is a judgement call: continue, escalate to legal, extend, or recommend closure.

When an Active collection period is within 30 days of ending, Debitura automatically creates one Update Case Status task for that case — the same task type used for the routine monthly cadence — even if your account is otherwise on DecisionPointOnly. This is the one update that survives automation: it exists specifically to capture the end-of-period judgement call. It follows the same request timing as everyone else, so if you already have an unresolved case-update task open for that case, a new one isn't created on top of it.

You can also track the period yourself instead of waiting for the task:

GET /cases/{id}/exclusive-period

This returns the full period chain, including any extensions triggered by debtor actions. Poll it, or check it when a case's activity slows, if you want to anticipate the period end before the task appears.

Effect on Your Quality Score

The SLA component of your quality score weights case-update responses alongside case verification and chat replies. When update requests are no longer generated for you, the score renormalises across the remaining task types rather than counting the absent ones as missed. Automating your updates does not reduce your SLA score. The occasional period-end task described above is scored normally when it appears — it isn't held against you, and it's the reason this task type won't always be fully absent from your history.

Getting Switched Over

This is enabled by Debitura on your partner account, not self-serve. Contact partner@debitura.com once your integration is sending payments and case activity on a regular cadence with references that resolve.

Business context: See Automate Your Monthly Case Updates for the full onboarding process, and for the file-based submission route if API integration isn't an option for you.

API Endpoints

Endpoint	Purpose
POST /cases/{id}/payments	Record a payment
POST /cases/{id}/notes	Record case activity on one case
POST /ingestion-jobs	Batch case activity, up to 1,000 rows
GET /ingestion-jobs/{jobId}	Poll batch progress
GET /cases/by-partner-reference/{reference}	Resolve your reference to a case, single lookup
GET /cases/by-partner-reference?references=	Resolve your reference to a case, batch lookup up to 100
GET /cases/by-creditor-reference	Resolve the creditor's reference to a case
GET /cases/{id}/exclusive-period	Collection period chain and end date
GET /me	Your partner account, including surveyCadenceMode

For full endpoint documentation, see the API Reference.