Bit2Me APIAccount model
Parent account, subaccount, and pocket hierarchy on the Bit2Me API.
The gateway uses three layers. Get this model right before you fund, trade, or withdraw.
| Layer | What it is | How you identify it |
|---|---|---|
| Parent | Master account created by Bit2Me and authenticated with your API keys. Parent accounts must complete KYB before operating. | API key pair |
| Subaccount | One wallet namespace per end user (or per corporate client). Must complete KYC (person) or KYB (type: company) before operating. Unlimited end users; each user = exactly one subaccount. | userId UUID in X-SUBACCOUNT-ID |
| Optional sub-ledger per currency (EUR, BTC, ETH, …). You can also operate at wallet level. | Pocket UUID |
Subaccount header
After you create a subaccount, send:
X-SUBACCOUNT-ID: {userId}HTTP header names are case-insensitive. Samples in this portal use X-SUBACCOUNT-ID. Parent HMAC headers still apply. If this header is missing, you operate the parent account — a common cause of “empty balance” tickets.
Onboarding
- Natural person: KYC until
status: verifiedandtier: 2. - Legal entity: KYB. Do not call identity init on companies.
Funding note
A minimum fiat balance is required to operate. As part of the initial setup there is a one-time fiat transfer to the account Bit2Me gives you during onboarding. If you are a bank, the parent fiat account is held in your own institution.
Day-to-day fiat is funded to the main account. Keep your own ledger of the fiat balance of each subaccount.
Fiat funding supports EUR and BRL (Fiat deposits and withdrawals); ARS is not available yet. USD is only available on Bit2Me Pro — contact sales if you need it.