Record a decision's real-world outcome by the client's correlation key
instead of our decision_id — the path a real event takes. A chargeback, refund reversal, or human override knows the order/case id it happened to, not the…
POST
instead of our
decision_id — the path a real event takes. A chargeback,
refund reversal, or human override knows the order/case id it happened to,
not the decision id we returned; this closes the outcome loop from those
events. Targets the most-recent decision carrying the ref. 404 if no
decision with that ref is in the retained window.
Required scope: write
Request body
RecordOutcomeByRefRequest
string
required
The client correlation key the decision was made about (order id, case id, claim number) — supplied as
external_ref on the decision request.string
required
honored | reversed | overridden | escalated.Response
RecordOutcomeResponse
boolean
required