This section describes the public endpoints of the Travel Rule Protocol (TRP) Registry API. These endpoints allow third-party systems and Virtual Asset Service Providers (VASPs) to discover, identify, and register participants in the TRP network.
The API follows REST conventions and returns responses in JSON format. All requests should be made over HTTPS.
The TRP API enables VASPs to:
- Authenticate using API keys
- Generate unique Travel Addresses for beneficiaries
- Initiate Travel Rule transfers
- Exchange originator and beneficiary data securely
- Receive callback notifications from TRP during the verification process
TRP follows global compliance standards (FATF, IVMS101) and ensures secure, encrypted communication between VASPs.
Every integration follows one simple flow:
- Request JWT token → authenticate your VASP
- Generate Travel Address → unique identifier for the beneficiary VASP
- Initiate Transfer → send IVMS101-compliant data
- Receive callback → TRP sends status updates to your backend
Before calling any protected endpoint, your system must generate a JWT access token using your API Key.
This ensures:
- Secure API access
- Verified VASP identity
- Ability to track API usage
- Authorization for initiating Travel Rule transfers
The access token is short-lived (TTL = 1 hour) for security reasons.
This is the first step in every API session. You send your API Key and receive a temporary JWT token.
- Protects the API
- Prevents unauthorized access
- Ensures every transfer is linked to a verified VASP
A Travel Address is a unique identifier for the beneficiary VASP. It acts like a Travel Rule routing code that tells TRP where to deliver IVMS101 beneficiary data.
To generate it, you only provide:
- Beneficiary first name
- Beneficiary last name
No sensitive data is exposed.
- Before initiating a transfer
- When a user enters a beneficiary’s wallet address
- During onboarding flows
The Travel Address:
- Identifies the beneficiary VASP
- Defines where TRP sends IVMS101 data
- Ensures cross-platform interoperability
- Eliminates manual data entry risks
This is the main Travel Rule operation.
You submit:
- Originator data
- Beneficiary data
- Asset and amount
- Travel Address
- Callback URL
TRP will:
- Validate IVMS101 originator & beneficiary data
- Determine the beneficiary VASP from the Travel Address
- Forward the data securely
- Await their confirmation
- Send callback updates to your backend
Once the transfer request is received:
- Validates IVMS101 originator & beneficiary data
- Identifies beneficiary VASP via Travel Address
- Routes data securely
- Waits for beneficiary’s decision
- Sends callback notifications to your backend