Bit2Me APICrypto withdrawals (address book)
Verify the destination, draft without type, then POST /v2/.../draft{orderId}. Do not call travel-rule-order.
This page describes the published API. It is not legal advice. Bit2Me Legal and Compliance must review KYC, KYB, Travel Rule, and 2FA copy before this portal is announced to partners.
This is the current OpenAPI target path for subaccount crypto out. The Wallet proforma path remains live — see Wallet legacy. Follow the API response. Do not invent address-book TTLs or sunset dates.
Once the withdrawal address is validated, Travel Rule data is already on the address-book entry. Do not call POST /v2/blockchain-manager/travel-rule-order/{orderId}. That call belongs to Wallet legacy only.
Verify the destination wallet first
The first time a subaccount withdraws to a new on-chain address, you must save that destination and confirm it with 2FA before any funds move. OpenAPI: the entry may require confirmation before it can be used.
POST /v1/blockchain-manager/address-book— create the destination, includingwalletType,walletOwnership, andexchangeNamewhen required.POST /v1/compliance/address-book/{addressBookId}/confirm— verify it (x-totp+x-totp-type: gauth). 204. Idempotent if already approved.
Do not call withdrawal draft until that confirmation succeeds (or the entry is already verified). Later withdrawals to the same confirmed entry reuse addressBookId. They do not need a new address-book create. Confirm again only if you create a new entry.
Prerequisites
- Subaccount KYC or KYB complete.
- Google Authenticator enabled. For subaccounts,
x-totp-typeis alwaysgauth. - Destination address, network, and wallet declaration on the address-book create (
walletType,walletOwnership;exchangeNamewhen type isexchange).
POST /v1/blockchain-manager/address-bookAlways send address, currency, network, walletType (unhosted or exchange), walletOwnership (own or other). Add exchangeName when the type is exchange. Optional tag for memo/destination tag.
201 includes addressId and status: validating | verified | expired. 409 means an active entry already exists.
How long validating lasts before expired is not published.
POST /v1/compliance/address-book/{addressBookId}/confirmSubaccounts cannot use the email confirmation token. Confirm with TOTP instead. 204. 403 if not a subaccount. 420 invalid 2FA. Idempotent if already approved.
Per-movement confirmation (/v1/compliance/blockchain-address-confirmation/wallet-movement/...) is deprecated. Use this address-book confirm instead.
POST /v1/blockchain-manager/order/withdrawal/draftBody: addressBookId plus amount.value / amount.currency. Do not send type.
amount is REA only. The value is the amount that will be attempted to be sent, and the network fee is added on top. The pocket must cover that amount plus the current network fee. SEA (state an amount and subtract the fee from it) is the Wallet proforma behavior. It is not available on this call.
The draft requires a verified address-book entry. No funds move. Use expiresAt from the 201 body — OpenAPI does not publish a fixed lock in minutes.
POST /v2/blockchain-manager/order/withdrawal/draft{orderId}This path is written without a slash before {orderId}. Do not insert one, and do not add a body that was not stated. It is not the same call as POST /v1/blockchain-manager/order/withdrawal/draft/accept (that accept takes draftId in the body).
Do not call POST /v2/blockchain-manager/travel-rule-order/{orderId}. walletType, walletOwnership, and exchangeName are already on the verified entry.
The blockchain-manager orderId is not the wallet transaction id. Do not read it with GET /v1/wallet/transaction/{orderId}. It is not the id on wallet.* WebSocket events, including wallet-transaction-v1. It is not confirmed to be a teller id.
These lookups are known and not prioritized: Wallet transactions by this OrderID, all orders of a user, and one order by OrderID.