Skip to main content

Tasks

Reference for Debitura's task model — the action items that surface when a case (or your account) needs something from you before it can keep moving.

Business context: See Tasks in Debitura for how action items are created and managed.

What Is a Task?

A task is Debitura's "you must do X before this can proceed" prompt — reply to a partner's chat message, sign a contract, assign a bank account, and so on. Tasks are created automatically as a case progresses through its lifecycle, and they auto-resolve once the underlying condition clears — there's no separate "mark as done" call. Treat a task list as a live work queue, not an append-only log: a task seen on one call may no longer be open on the next.

Task Types

TypeWhat it meansScopeAPI-resolvable
ReplyToChatA partner is waiting on your reply in the case chatCaseYes
ClientInputRequiredA partner needs additional information from you, via chatCaseYes
MoreInfoNeededSame as above — a partner requested more detail before proceedingCaseYes
SelectQuoteWinnerPick the winning quote on a lead before it becomes a caseCaseNo — resolve via solutionUrl
ReviewPartnerSubmit an NPS-style rating for the collection partner on a closed caseCaseNo — resolve via solutionUrl
SignContractSign or re-sign the SDCA / Power of AttorneyAccountNo — resolve via solutionUrl
AssignBankAccountAttach a payout bank account — blocks case processing until setAccountNo — resolve via solutionUrl
CaseValidationNeedsInfoCase Validation flagged missing or inconsistent case dataCaseNo — resolve via solutionUrl
GenericA miscellaneous action item without a dedicated typeCaseNo — resolve via solutionUrl

SignContract and AssignBankAccount are account-level: they aren't tied to a single case, so they only ever appear in an account-wide task listing, never in a case-scoped one.

Every Task Has a Solution URL

Every task carries a solutionUrl — an absolute link, identical to the one used inside the Debitura app itself, that resolves the task in one click. This is the one guaranteed way to resolve any task type, even ones that aren't (yet) directly actionable through an API — no polling loop needed, just surface the link to whoever handles that task on your side.

API-Resolvable vs. solutionUrl-Only

Some task types are directly resolvable through an API call — these additionally carry an action (an HTTP method + path) describing the exact call that resolves them, so an integration can act without a human opening solutionUrl. Task types without a wired-up action carry action: null and rely on solutionUrl alone. Which types are API-resolvable depends on what the underlying API surface already supports — for example, chat-driven task types resolve through whatever endpoint already posts a chat message on that surface, so no dedicated "resolve task" endpoint is needed for them.

Where This Is Implemented Today

The Customer API exposes the table above for creditor accounts — see Tasks and Action Items for the request/response shape, filtering, and how to resolve chat-driven tasks via the API.