FIfireblocks
TRLink

Manual decision for missing TRM

Accept or reject destinations waiting for a Travel Rule message (missing TRM), without waiting for a TRP webhook or the missing-TRM policy timeout. You can submit before a destination enters the missing-TRM wait; if it can't be updated immediately, the decision is applied on the next processing attempt instead (status ACCEPTED). Check status in the response to see whether the decision has been applied.

post/screening/trlink/customers/integration/{customerIntegrationId}/transactions/{txId}/manual_decision

Request

Path parameters

customerIntegrationIdstring uuid required

Customer integration unique identifier

txIdstring uuid required

Fireblocks transaction unique identifier

Headers

Idempotency-Keystring

A unique identifier for the request. If the request is sent multiple times with the same idempotency key, the server will return the same response as the first request. The idempotency key is valid for 24 hours.

Request body

action'ACCEPT' | 'REJECT' required

Decision action for destinations waiting for a Travel Rule message (missing TRM)

reasonstring

Optional reason for the manual decision (e.g. 'Internal KYC approved'). Do not include PII.

Example request

{
  "action": "ACCEPT",
  "reason": "Internal KYC approved"
}

Response

Decision applied (status APPLIED), accepted for the next processing attempt (status ACCEPTED), or accepted early (status PRE_ACCEPTED).

status'APPLIED' | 'ACCEPTED' | 'PRE_ACCEPTED' required

APPLIED - Decision applied to at least one destination immediately. ACCEPTED - Intent stored for deferred apply on the next processing attempt. PRE_ACCEPTED - Intent stored on the transaction before destinations entered the missing-TRM wait.

action'ACCEPT' | 'REJECT' required

Decision action for destinations waiting for a Travel Rule message (missing TRM)

source'manual' | 'policy' required

Source of the manual decision. Values are lowercase.

txIdstring required

Transaction ID

destinationsAffectedinteger required

Number of destinations where the decision was applied

destinationsSkippedinteger required

Number of destinations that were skipped

Example response

{
  "status": "APPLIED",
  "action": "ACCEPT",
  "source": "manual",
  "txId": "b70701f4-d7b1-4795-a8ee-b09cdb5b850e",
  "destinationsAffected": 2,
  "details": [
    {
      "destinationScreeningId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
      "applied": true,
      "skipReason": "deferred apply"
    }
  ]
}

Changes

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