API overview

How to use the generated Wallet OpenAPI reference on this site.

The REST tab lists every gateway operation published for Wallet, grouped in sections: Access, Wallet, Earn, Account, KYC, Funding, Compliance, Transfers, Market, Loan, Misc. Server: https://gateway.bit2me.com.

TagWhat it is
AccessHMAC POST /v1/signin/apikey (session token for widgets and Pro WS) vs POST /v1/signin/embed (embed token exchange — not HMAC API-key sign-in)
MarketWallet catalog (/v1/currency/…, /v2/currency/…). This is not the Spot Trading API Market Data section (/v1/trading/candle, /v2/trading/order-book)
Wallet / FundingPockets, transactions, teller deposits, crypto withdrawals
KYC / Account / ComplianceSubaccounts, identity, address book, Travel Rule

Spot trading REST lives under Spot Trading API.

Playground

Private endpoints require HMAC (x-api-key, api-signature, x-nonce). The playground signs them in your browser once you enter your key and secret under Authorization; they apply to every endpoint until you reload. It calls production, so prefer a read-only key. See Playground.

Postman

Import the OpenAPI specification into Postman:

  • By link: in Postman, go to Import → Link and paste https://gateway.bit2me.com/docs/openapi.json.
  • By file: download openapi.json, then Import → File.

Postman does not compute the HMAC signature for you: add a pre-request script that signs each call, as in Authentication.

On this page