/recollection-case/{recollection_case_id}/set-objective

post

https://api-sandbox.getdefacto.com/recollection-case/{recollection_case_id}/set-objective

Set a recollection case's collection objective

Set the case's estimated recoverable amount over exactly three horizons (within 5 business
days, within a month, ever), the collection phase, and the justification. Governed by the
recollection policy §4/§9: the reasoning must assess the borrower's liquidity and near-term
trajectory, with a likelihood stated per horizon.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

recollection_case_id

string

required

Body Params

collection_phase

string

enum

required

Allowed:

objective

array of objects

required

length between 3 and 3

Exactly 3 horizons, in order: within 5 business days, within a month, ever.

objective*

confidence

string

enum

required

Allowed:

date

pct_recovered

integer

required

0 to 100

Estimated recovery percentage for this horizon, an integer 0-100.

confidence

string

enum

required

Allowed:

date

pct_recovered

integer

required

0 to 100

Estimated recovery percentage for this horizon, an integer 0-100.

confidence

string

enum

required

Allowed:

date

pct_recovered

integer

required

0 to 100

Estimated recovery percentage for this horizon, an integer 0-100.

objective_comment

string

required

Justification for the stated objective.

Headers

X-Decision-Id

uuid

required

UUID of an approved governance Decision whose planned_operations list this endpoint together with the exact request payload. The matching planned step must not yet have been executed. Planned operations may contain {{step.<n>.json.<path>}} references to earlier steps' responses: the gate resolves them against the recorded outputs before matching, so send the RESOLVED body and fire steps in order — a step whose references are not yet resolvable cannot match. Required for MCP callers; HumanReviewer callers bypass the gate by default.

Responses

400

Missing X-Decision-Id header or value is not a valid UUID.

403

Decision is not approved, the calling identity does not match the proposer, no planned operation matches this endpoint + payload, the matching step has already been executed, or the caller is not a recognised proposing Operator.

404

No Decision exists for the supplied X-Decision-Id.

Language

Credentials

Header

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

*/*

200