Skip to main content
An Outcome is a result your system has already assigned, such as an onboarding decision, fraud alert, or investigation disposition. It records source evidence; uploading an outcome does not mean Karsa independently reached the same conclusion.

What to send

Exactly one subject field must contain a resourceId; the other three must be null or omitted.

Upload an outcome

Subject semantics

Use a Customer outcome for a result about the customer as a whole. Use a Transaction or Document outcome only when the result belongs specifically to that record. Outcomes do not accept arbitrary customData; the type, value, subject, and version metadata are the complete shape.

Versioning and deduplication

Send the same externalId with a new idempotency key when the source outcome changes. A corrected value appends an OutcomeVersion; it does not overwrite the earlier result.
  • Customers: upload a customer before attaching a customer outcome
  • Transactions: attach a result to a specific transaction
  • Documents: attach a result to a specific document