Get Travel Rule Settings
Read the application’s Travel Rule settings and VASP profile. Auto-creates a default (disabled) settings row and an empty profile on first read.
Authorizations
Response
Current Travel Rule settings and VASP profile.
Whether the managed Travel Rule negotiation flow is active for outbound travelRule transactions on this application.
Your VASP's operating jurisdiction code. Default "EU".
8How strictly beneficiary names must match before a transfer can reach COMPLETED.
NONE, STRICT, DEFAULT, FUZZY Hours an AWAITING_COUNTERPARTY transfer may remain unconfirmed before the periodic sweeper expires it. Default 48.
x >= 1What happens to the underlying transaction when a transfer expires. Default HOLD.
HOLD, REJECT, PROCEED Decimal string. Minimum transfer amount that triggers a managed exchange; transfers below it resolve straight to NOT_APPLICABLE. Defaults to "0.00" (EU TFR applies no minimum amount).
Your VASP's legal name. Required (non-blank) to set is_enabled to true.
Your Legal Entity Identifier, surfaced in the VASP directory.
Compliance contact email for your VASP profile.
Whether your VASP profile appears in GET /v3/travel-rule/vasps/ search results and can be reached on the INTERNAL rail. Default true.
When true, inbound transfers whose beneficiary wallet is a verified address-book entry with a matching name are accepted automatically, without a manual review step. Default false.
When true, the wallet-ownership widget offers self-declaration as a fallback proof method. Default false.
When true, the wallet-ownership widget offers screenshot upload as an ownership evidence method. Default true.
When true, submitting an outbound Travel Rule transfer that needs end-user proof of wallet control auto-mints a wallet-ownership widget session bound to the transaction and exposes it in the transaction's action_required block. Default true.
When true, an outbound Travel Rule transfer that no rail can route is attributed through blockchain analytics: the destination wallet is resolved to its owning VASP, the entity is recorded on the transfer and in the VASP directory, and the rails are re-run once with the attributed name. Default true.
Read-only. Your VASP's own travel address - the encoded inbound TRP inquiry endpoint other VASPs use to reach you. Populated once your VASP profile is complete.