Market makers
Professional market-making firms benefit from the Market-Making Program, which offers maker rebates up to -0.012%, colocation infrastructure in Frankfurt and Tokyo (3-5ms latency), and bulk order capabilities (up to 20 orders per call). The program includes a dedicated account manager and cross-marketing support. For the complete integration walkthrough, see the Market Maker Guide.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. For the complete integration walkthrough, see the Broker Guide.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 a complete automated trading workflow. The WebSocket Quickstart covers real-time data streaming. Key technical considerations:- Rate limits: polling frequency must stay within per-endpoint limits; WebSocket streaming is recommended for real-time data to reduce REST polling
- Kill-switch: emergency mechanism to cancel all open orders after a configurable timeout — critical safety feature for unattended bots
- Order Types: Market, Limit, Stop-Limit, Stop-Market, Stock-Market, and Bulk-Limit — availability varies by market type
- Client Order ID: attach custom identifiers to orders for tracking across systems
- Use sub-accounts for strategy separation when running multiple bots
- Consider colocation (3-5ms latency) 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 surveillance
WhiteBIT does not offer a public testnet. Test all trading flows on the live API with minimum order amounts. Use
GET /api/v4/public/markets to find pairs with the lowest minimum order sizes for testing.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 complete deposit/withdrawal lifecycle, fee calculation, and status state machines. Review Webhooks for real-time transaction notifications and Regulatory Compliance for EEA-specific requirements. Key considerations:- Travel Rule: EEA crypto withdrawals require a
travelRuleobject with beneficiary information - MiCA compliance: USDT operations are restricted for EEA users since December 30, 2024 — 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, use the Convert feature with a Main → Trade → Convert → Trade → Main transfer pattern — see Payment Integration for the full flow
- Primary: webhook-based notifications for deposits and withdrawals
- Fallback: poll the deposit/withdraw history endpoint for reconciliation
- Deduplication: use
uniqueIdacross 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 flexible multi-account structures for managing multiple traders and strategies under one organization. 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 3-5ms access from Frankfurt and Tokyo
- Market-Making Program — maker rebates for firms running spread-capture or liquidity strategies
- 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
Institutional clients
Institutional clients — including hedge funds, asset managers, family offices, banks, fintechs, and exchanges — access the full product suite through institutional onboarding. The onboarding process covers KYB verification, fiat access approval, and dedicated account management. The institutional product 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
| Use case | Recommended | Reason |
|---|---|---|
| Live prices | WebSocket (lastprice channel) | No polling needed; instant updates |
| Orderbook depth | WebSocket (depth channel) | Real-time depth snapshots |
| Place / modify / cancel orders | REST API | Request-response pattern with confirmation |
| Monitor balances | WebSocket (balanceSpot / balanceCollateral) | Real-time balance changes |
| Fetch historical trades | REST API | One-time queries, paginated |
| Check open orders | REST or WebSocket | REST for on-demand; WebSocket for real-time |
What’s Next
First API Call
Make a first authenticated API call in 5 minutes.
SDKs
Official SDKs in Go, Python, and PHP.