Outcome Feedback

Report what actually happened after a Scout scan

FLINT cannot stop a wallet; this is the enforce-or-attest half of the contract. Reports whether the scanned transaction executed, was held, or was cancelled. Auth is one of: a bearer or cookie session whose account owns the passport presented on the record, the anonymous caller_binding_token issued with the scan (open security, no scheme), or a partner service credential. Idempotent: the first write wins and a later write returns 409 with the existing outcome. Reporting executed or executed_despite_block after a BLOCK verdict is stored as an override, appended to the passport ledger, and alerts the passport owner through Sentinel.

post/api/records/{record_id}/outcome

Request

  • Base URL: https://flint.network
  • URL: https://flint.network/api/records/{record_id}/outcome
  • Auth: one of:
    • none
    • API key in cookie flint_session
    • HTTP bearer
    • HTTP bearer

Path parameters

record_idstring required

FLINT verification record identifier.

Request body

outcome'executed' | 'held' | 'executed_despite_block' | 'cancelled' required
tx_hashstring

Required when outcome starts with executed.

chainstring
notestring
caller_binding_tokenstring

Required to report anonymously as the caller instead of via session or partner credential.

Response

Outcome recorded.

okboolean required
record_idstring required

Changes

No recorded changes to this operation across all 1 revision of this API.