Submits required data (e.g., beneficiary PII) to resolve a pending Travel Rule Message action.
Documentation Index
Fetch the complete documentation index at: https://developers.fireblocks.com/llms.txt
Use this file to discover all available pages before exploring further.
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.
Customer integration unique identifier
Travel Rule Message unique identifier
Request to resolve a pending TRM action
The action type identifier as defined by the Travel Rule provider. Must match one of the types returned by the get required actions endpoint. Values are provider-specific and may vary across different TRP implementations.
"UPLOAD_BENEFICIARY_PII"
Data to submit when resolving an action. The structure varies by action type and is validated by the TRP provider.
For UPLOAD_BENEFICIARY_PII action type: Contains beneficiaryPii with IVMS101-encoded PII data.
Action resolved successfully
Travel Rule Message information
TRM message ID
"trm_1234567890abcdef"
External ID (e.g., Fireblocks ID)
"550e8400-e29b-41d4-a716-446655440000"
Transaction amount in asset units
"1000"
Transaction direction for TRM (in = inbound, out = outbound)
in, out "out"
IVMS101 data in response format
TRM version
"1.0"
Current status of the Travel Rule Message
PENDING, ACCEPTED, REJECTED, FAILED "ACCEPTED"
Human readable reason for the current status
"Travel Rule compliance required for this transaction"
ID of the originator VASP
"did:ethr:0x1234567890abcdef"
ID of the beneficiary VASP
"did:ethr:0xfedcba0987654321"