How to set up a Sub-Account on OKX for different strategies? (Management)

Sub-Account Initialization Process

1. Log in to the OKX web platform using your primary account credentials.

2. Navigate to the “Assets” section and select “Sub-Account Management” from the dropdown menu.

3. Click “Create Sub-Account”, enter a unique name, and assign a dedicated email address for notification routing.

4. Confirm creation by completing SMS or hardware wallet verification as prompted.

5. Immediately assign API permissions scoped to strategy-specific functions—no blanket “full access” grants are permitted.

Permission Granularity Control

1. Each sub-account supports role-based access control (RBAC) with pre-defined templates: “Spot Trader”, “Derivatives Analyst”, and “Risk Monitor”.

2. Custom permission sets can restrict API endpoints to exact methods—e.g., allowing GET /api/v5/account/balance but blocking POST /api/v5/trade/order.

3. Withdrawal rights are disabled by default and require separate approval via email confirmation signed with the master account’s passphrase.

4. IP whitelisting is enforced per sub-account; no shared proxy or NAT gateway addresses are accepted during setup.

5. Time-bound permissions can be scheduled—for example, enabling futures leverage adjustment only between 08:00–16:00 UTC on weekdays.

API Integration for Multi-Strategy Deployment

1. Initialize the SubAccountAPI module using distinct credential sets per sub-account: SubAccount.SubAccountAPI(api_key_a, secret_key_a, passphrase_a, False, '0').

2. Use get_subaccount_list() to retrieve active identifiers before executing any balance or order operations.

3. Batch asset queries must specify comma-separated sub-account names—not IDs—to avoid internal mapping errors in v5 response parsing.

4. Leverage mode configuration requires prior validation of margin tier eligibility via get_subaccount_margin_ltv(), which returns real-time LTV thresholds per instrument class.

5. Order placement through sub-accounts enforces TD-mode isolation: cash, margin, and portfolio margin modes cannot be mixed within a single sub-account context.

Funding Flow Orchestration

1. Internal transfers between sub-accounts execute instantly with zero fees and no blockchain confirmation delay.

2. The funding.transfer() method mandates explicit specification of both source and target sub-account names—not just IDs—to prevent accidental cross-strategy fund movement.

3. Transfer history is logged separately per sub-account and does not appear in the master account’s general ledger unless explicitly aggregated via reporting API.

4. Automated funding rules can be defined using time-triggered scripts that invoke set_subaccount_level() to adjust risk exposure caps before market open.

5. Negative balances are prohibited at the sub-account layer; any attempted over-withdrawal triggers immediate suspension until manual override by the master account holder.

Common Questions & Direct Answers

Q: Can a sub-account generate its own API key independent of the master account?A: No. All sub-account API keys must be created under the master account’s API management interface and are bound to its security policies and audit trail.

Q: Is it possible to view PnL across multiple sub-accounts in a single consolidated report?A: Yes. The get_subaccount_pnl_summary() endpoint accepts a list of sub-account names and returns unified daily, weekly, and monthly PnL figures with instrument-level breakdowns.

Q: What happens to open orders when a sub-account is deleted?A: All pending orders are automatically canceled prior to deletion. No partial execution or orphaned state is permitted.

Q: Do sub-accounts inherit the master account’s KYC level?A: Yes. Sub-accounts operate under the same jurisdictional compliance tier as the master account; no individual KYC submission is required or allowed.