Bit2Me APIPartner REST overview
Embed reference plus the Wallet routes partners actually call.
The Partner REST tab lists the operations published for Embed: create subaccount, HMAC sign-in with userId, and the callbacks Bit2Me posts to your backend.
Those callbacks are webhooks: you implement POST /v1/b2m/transaction/authorize (approve or reject a widget operation) and POST /v1/b2m/transaction/report (Bit2Me notifies you that a widget operation happened). report is not Travel Rule. Submit Travel Rule on the gateway: Travel Rule (POST /v2/blockchain-manager/travel-rule-order/{orderId}).
Most partner money movement is on the Wallet REST reference.
| Area | Spec |
|---|---|
| Widgets / session | Partner REST tab |
| KYC, pockets, teller, withdrawals | Wallet REST |
Wallet REST operations partners call
Use these generated Wallet REST pages. Sign HMAC on your backend.
| Need | Call | Reference |
|---|---|---|
| Create end-user subaccount | POST /v1/account/subaccount | Create subaccount |
| Person KYC session | POST /v3/account/verify/identity/init | Init KYC verification |
| Create a currency pocket | POST /v1/wallet/pocket | Create pocket |
| Bank-transfer deposit details | GET /v1/teller/pocket/reference | Get pocket reference |
| Card / Apple Pay / Google Pay / PIX | POST /v1/teller/order/proforma | Create deposit |
| Verify a crypto destination (first time) | POST /v1/blockchain-manager/address-book | Create an address book entry |
Travel Rule (Wallet legacy only, when the operation is pending_user_information) | POST /v2/blockchain-manager/travel-rule-order/{orderId} | Travel Rule |
| Pay a Bit2Me user | POST /v1/social-pay/order (Transfers) | Transfers |
| Wallet → Pro / Pro → Wallet | POST /v1/trading/wallet/deposit · withdraw | First order |
HMAC session for widgets and Pro WS is POST /v1/signin/apikey, not POST /v1/signin/embed. See Authentication.
Each reference page can send a signed request with your key, from your browser, against production. See Playground.