Bit2Me APIComplete travel rule order
/v2/blockchain-manager/travel-rule-order/{orderId}Submits the travel-rule information of a crypto order of the authenticated user: who the counterparty is and what kind of wallet they use. For a deposit that is who sent the funds, and for a withdrawal who receives them.
Compared with POST /v1/blockchain-manager/travel-rule-order/{orderId}, the counterparty's address is
reduced to its country (address.countryCode), identity documents, place of birth and date of
birth are not collected, and ownershipVerified can be sent for unhosted wallets.
When walletOwnership is other, personType, name and address are required, and surname
too unless personType is company.
Authorization
ApiKeyAuth For accessing these endpoints a valid API key must be sent in the X-Api-Key header.
In: header
Path Parameters
ID of the crypto order (deposit or withdrawal) the information refers to.
^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$uuidRequest Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Information about the counterparty of the order and their wallet: who sent the funds of a deposit, or who receives the funds of a withdrawal.
When walletOwnership is other, personType, name and address are required, and surname
too unless personType is company.
Response Body
application/json
application/json
application/json
application/json
application/json
curl --request POST \ --url 'https://gateway.bit2me.com/v2/blockchain-manager/travel-rule-order/550e8400-e29b-41d4-a716-446655440030' \ --header 'Content-Type: application/json' \ --data '{ "address": { "countryCode": "ES" }, "exchangeName": "Binance", "name": "John", "personType": "person", "surname": "Doe", "walletOwnership": "other", "walletType": "exchange"}'Travel-rule information accepted. The response has no body.
Get pocket reference GET
Returns the reference to deposit into a pocket by bank transfer, together with the bank accounts that accept the deposit. To fund the pocket, send a transfer to any of the accounts in `bankAccounts` with `pocket.reference` as the concept. The reference is assigned the first time it is requested and stays the same afterwards.
Confirm an address book entry POST
Confirms a destination address in the address book without needing the email-based confirmation token. Intended for subaccounts that cannot receive the confirmation email directly. The authenticated user is treated as the address book owner. The operation is idempotent: if the entry is already approved the endpoint returns `204` without error. TOTP is sent via the `x-totp` header; only `gauth` is supported as delivery method.