Partner Solutions

WhiteBIT partners integrate through program funnels — one per partner type. Pick a partner type from the cards, or use the three structural questions to route an overlapping label. Each path leads to a program overview, an integration guide, and a program FAQ. Partner programs are approval-gated — see How to apply.

​

Choose an integration path

Partner labels overlap (a single business can span two different architectures), so the fastest routing comes from three structural questions:

1. Account holding — do end users hold personal WhiteBIT accounts, or does the partner operate accounts on the end users’ behalf? Own accounts with a partner-held API key are Model B → App Builders. Partner-operated sub-accounts are Model A → Embedded Trading. Compare the two models on the integration models concept; building a full backend instead of a single account model → compare Wallet-as-a-Service and Crypto-as-a-Service.
2. Direction — is the partner building on the WhiteBIT API, or proposing WhiteBIT integrate into an external platform or network? The latter is a partnership conversation — contact institutional@whitebit.com directly (see Funds & Institutions).
3. Scope — trading, payments, or both? Payment and payout integrations route to Payments & Fiat regardless of the answers above.

Common use cases mapped to a program:

​

REST vs. WebSocket decision matrix

Order placement runs over REST for request–response confirmation and atomic bulk placement; the WebSocket order methods add an alternative on the same authorized connection from September 2, 2026, on the global platform only. Combining REST for order management with WebSocket for market data remains the most common integration pattern. See the WebSocket API for the available channels and the API Reference for endpoint details.

​

How to apply

Partner-program applications go to institutional@whitebit.com and are individually reviewed before provisioning. Including the following in the first message routes the application to the right team without extra clarification rounds: About the company (all applicants):

1. Registered legal entity — full legal name, registration number, and jurisdiction (not a brand or product name).
2. Licenses or registrations held, with the regulator and register reference. Unlicensed platforms qualify for models where WhiteBIT verifies end users directly; KYC reliance is separately gated — see the Wallet-as-a-Service page for the eligibility conditions.
3. Application capacity — the applicant’s own behalf or on behalf of a client — and the intended contracting counterparty.

About the integration (all applicants):

4. Direction — building on the WhiteBIT API, or proposing WhiteBIT integrate into an external platform or network (the latter is a partnership conversation rather than an application).
5. Intended account structure: (a) own main account only; (b) end users’ own WhiteBIT accounts with a partner-held API key; (c) per-customer sub-accounts under the partner’s master (main) account; (d) a pooled (omnibus) structure — a pooled account for end-user funds is not offered, but declaring the intent lets WhiteBIT propose the closest supported model (see why not a pooled account).
6. Scope — crypto only, or fiat as well, and at which level (partner account or end users).

About end users (partners serving end users):

7. The party performing end-user KYC — the partner or WhiteBIT — and, for partner-side KYC, the supervisory basis.
8. The user population reached — direct clients, or customers of the partner’s merchants or clients — and the business vertical.
9. The countries where the service is offered or marketed, and the geo-gating approach (how the service restricts availability by user country or region).
10. For sub-account requests: settlement topology — per-customer deposit addresses, or deposits and withdrawals concentrated at the master account with internal allocation.

​

Program terms and security

Program terms — revenue share and eligibility — differ by program; the specific band and how the share is reported are on each program overview. Security certifications apply platform-wide. Revenue-share terms depend on the program. Embedded Trading partners earn a share of the trading fees that referred customers generate across all products, with payouts initiated by the partner, most commonly once per month — see WhiteBIT Embedded Trading for current rates. Other partner programs confirm commercial terms during onboarding.

​

What’s next