Integration Paths

WhiteBIT supports six partner types: market makers, brokers, algo traders, payment providers, prop trading firms, and institutional clients. Each section lists the program terms, the relevant endpoints, and the next guide to read.

​

Market makers

Professional market-making firms benefit from the Market-Making Program, which offers maker rebates up to -0.012%, colocation infrastructure, and bulk order capabilities (up to 20 orders per call). The program includes a dedicated account manager and cross-marketing support. The Market Maker Guide covers the full integration walkthrough.

​

Brokers and trading platforms

Brokers and trading platforms integrate via the Broker Program, offering WhiteBIT liquidity to end users through a sub-account architecture. The program provides up to 40% fee share on trading fees generated by referred users, per-customer account isolation, and per-customer API keys. Brokers that need to issue per-customer API keys via OAuth (alongside or instead of the sub-account model) can use the Fast API Key via OAuth flow to bootstrap keys on behalf of users without manual copy-paste. The Broker Guide walks through the sub-account setup end to end.

​

Algo trading and bot providers

Algorithmic trading systems and trading bots integrate through a combination of REST API for order management and WebSocket for real-time market data. Start with the First API Call guide to verify connectivity and authentication. Then proceed to the Market Data Quickstart for real-time price feeds, the Spot Trading Quickstart for order placement, and the Trading Bot guide for an end-to-end automated trading workflow. The WebSocket Quickstart covers real-time data streaming. Key technical considerations:

• Rate limits: polling frequency must stay within per-endpoint limits; prefer WebSocket streaming for real-time data to reduce REST polling
• Kill-switch: emergency mechanism that cancels all open orders on a specified market after a configurable timeout (5–600 seconds) — critical safety feature for unattended bots
• Order Types: Market, Limit, Advanced-Limit, Stop-Limit, Stop-Market, Multi-Limit (Bulk), and OCO — availability varies by market type
• Client Order ID: attach custom identifiers to orders for tracking across systems

Infrastructure recommendations:

• Use sub-accounts for strategy separation when running multiple bots
• Consider colocation for latency-sensitive strategies
• Implement the kill-switch as a circuit breaker for all production bots
• Set up Account Monitoring for balance tracking, deposit/withdrawal alerts, and order activity monitoring

​

Payment and ramp providers

Payment providers and on/off-ramp services integrate deposit and withdrawal workflows to move funds programmatically. Start with the First API Call guide for authentication setup. Then proceed to the Payment Integration guide for the full deposit/withdrawal lifecycle, fee calculation, and status state machines. Review Webhooks for real-time transaction notifications and Regulatory Compliance for EEA-specific requirements. Payment and ramp providers that issue API keys on behalf of merchants can bootstrap keys through the Fast API Key via OAuth flow as an alternative to manual key generation. Key considerations:

• Travel Rule: crypto withdrawals from EEA accounts (and Turkey) require a travelRule object with beneficiary information
• MiCA compliance: since December 30, 2024, EEA accounts cannot deposit, withdraw, or create WhiteBIT Codes in USDT — use USDC or EURI as alternatives
• Webhook signature verification: validate HMAC-SHA512 on all incoming webhooks
• Currency conversion: when the held currency differs from the withdrawal currency, request a Convert quote, confirm it, and submit the withdrawal — the convert service routes balances internally with no manual Main ↔ Trade transfers. See Payment Integration for the full flow

Reconciliation:

• Primary: webhook-based notifications for deposits and withdrawals
• Fallback: poll the deposit/withdraw history endpoint for reconciliation
• Deduplication: use uniqueId across both channels
• See the Payment Integration guide for the full reconciliation strategy

​

Prop trading firms

Prop trading firms need deep liquidity, low-latency execution, and sub-accounts that isolate balances and API keys for each trader or strategy. Recommended products:

• Sub-Accounts — isolate strategies with independent balances and API keys; assign role-based access for traders, risk managers, and operations
• Colocation — minimize execution latency with co-located infrastructure
• Market-Making Program — maker rebates for firms running spread-capture or liquidity strategies

Infrastructure considerations:

• Use per-sub-account API keys with IP whitelists for security isolation between trading desks
• Block or unblock sub-accounts via API to enforce automated risk controls
• Monitor balances across all sub-accounts via POST /api/v4/sub-account/balances

Get started: apply through the prop trading program page or contact institutional@whitebit.com.

​

Institutional clients

Institutional clients — hedge funds, asset managers, family offices, banks, fintechs, and exchanges — access the institutional product catalog through institutional onboarding. The onboarding process covers KYB verification, fiat access approval, and dedicated account management. The catalog includes OTC Trading, Portfolio Margin (200,000 USDT minimum), Crypto-as-a-Service (CaaS), Wallet-as-a-Service (WaaS), and Custody solutions. See the Institutional Overview for the full product matrix and the Institutional Onboarding guide for the step-by-step process. Contact institutional@whitebit.com to begin the onboarding process.

​

REST vs. WebSocket decision matrix

Combining REST for order management with WebSocket for market data is the most common integration pattern.

​

What’s Next