> ## Documentation Index
> Fetch the complete documentation index at: https://docs.whitebit.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Sub-Accounts

> Create and manage thousands of separate trading accounts under one umbrella -- each with independent balances, API keys, and IP whitelists.

Create and manage thousands of separate trading accounts under one umbrella -- each with independent balances, API keys, and IP whitelists. 19 API endpoints cover the full lifecycle from account creation to withdrawal approval.

## Capabilities

The Sub-Accounts API provides full programmatic control over multi-account architectures.

* **Account CRUD** -- create, edit, delete, and list sub-accounts. Each sub-account gets a unique identifier and independent settings.
* **Fee-free instant transfers** -- move assets between the main account and any sub-account without fees or delays via `POST /api/v4/sub-account/transfer`
* **Per-sub-account API keys** -- generate dedicated API keys for each sub-account with independent IP whitelists (up to 50 IPs per key). The 50-key limit applies per sub-account, independent from the main account and from other sub-accounts. Supports create, edit, delete, reset, and IP management.
* **KYC URL generation** -- generate temporary KYC verification links for sub-account users via `POST /api/v4/sub-account/kyc-url`. Requirements: sub-account must be activated, active, and not using shared KYC.
* **Withdrawal approval flow** -- review and approve pending withdrawals from sub-accounts via `POST /api/v4/sub-account/withdraw/unconfirmed-list`. Only applies to sub-accounts of type "general" with the sub-account crypto service permission.

## Who Uses This

* **Fund managers and asset managers** -- separate client funds into isolated sub-accounts. Independent API keys per strategy or client. Fee-free transfers for rebalancing. ([Institutional sub-accounts](https://institutional.whitebit.com/sub-accounts))
* **Brokers and trading platforms** -- onboard end users as sub-accounts under the [Broker Program](https://institutional.whitebit.com/broker-program). Earn up to 40% of trading fees generated by referred users. Manage API keys centrally.
* **Prop trading firms** -- isolate trading strategies with separate risk profiles. Per-account balance monitoring. Independent position tracking.

## Common Integration Patterns

**Fund / Asset Manager** -- Create a sub-account per client or investment strategy. Generate independent API keys for each, allowing automated trading without exposing the main account. Transfer funds fee-free between the main account and sub-accounts for rebalancing. Monitor balances across all sub-accounts via `POST /api/v4/sub-account/balances`. Track transfer history via `POST /api/v4/sub-account/transfer/history`. *(Source: [institutional.whitebit.com/sub-accounts](https://institutional.whitebit.com/sub-accounts))*

**Broker / Agency** -- Apply to the [Broker Program](https://institutional.whitebit.com/broker-program) (contact [institutional@whitebit.com](mailto:institutional@whitebit.com)). Create sub-accounts for each end user. Generate KYC URLs for customer verification. Earn up to 40% of the trading fee generated by referred users (fee share applies to the base fee; [WBT](https://whitebit.com) -- WhiteBIT's native token -- holding can boost the share). Manage all sub-account API keys from the main account. *(Source: [Broker Program blog article](https://blog.whitebit.com/en/whitebit-broker-program-unlocking-new-dimensions-of-earnings/))*

<Note>
  **EUR/SEPA operations for brokers:** Fiat deposit and withdrawal functionality requires
  separate institutional onboarding through WhiteBIT and a fiat processing partner. See the
  [Onboarding Guide](/institutional/onboarding) for the full process.
</Note>

**Prop Trading Firm** -- Create isolated sub-accounts per trading strategy or desk. Assign different risk budgets by controlling the balance in each sub-account. Use per-sub-account API keys to run independent trading bots — traders, risk managers, operations, and finance teams can each have separately permissioned access. Block or unblock sub-accounts via API to enforce risk controls. *(Source: [institutional.whitebit.com/sub-accounts](https://institutional.whitebit.com/sub-accounts))*

## Technical Overview

* **19 endpoints** (all `POST`, all authenticated)
* **Endpoint groups:** account management (4), transfers (2), blocking (2), balances (1), API key management (6), IP whitelist management (3), KYC (1)
* **Authentication:** HMAC-SHA512 ([guide](/api-reference/authentication))
* **Rate limits:** 1000 requests per 10 seconds per endpoint ([details](/api-reference/rate-limits))
* **Permission requirement:** sub-account crypto service permission required for withdrawal approval endpoints

For full endpoint documentation, see the [Sub-Accounts API Reference](/api-reference/sub-accounts/overview).

## What's Next

<CardGroup cols={3}>
  <Card title="Quickstart" icon="rocket" href="/products/sub-accounts/quickstart">
    Create a sub-account and transfer funds in under 5 minutes.
  </Card>

  <Card title="API Reference" icon="square-terminal" href="/api-reference/sub-accounts/overview">
    Full endpoint documentation for all 19 sub-account endpoints.
  </Card>

  <Card title="Broker Guide" icon="handshake" href="/guides/broker-guide">
    End-to-end integration guide for the Broker Program.
  </Card>
</CardGroup>