Account Types
Use this reference to select account-type values for transfers and withdrawals. It covers DMA exchange accounts and RapidX Portfolios.
Recommended values and V1 compatibility
Use the standardized V2 account-type values below for new integrations, including integrations that call V1 endpoints. Existing supported V1 account-type values remain accepted, so existing integrations do not need to change immediately.
See Legacy V1 account-type reference for the original V1 transfer and withdrawal tables.
The enum naming convention is independent of the endpoint version:
| Account-type values | V1 transfer and withdrawal endpoints | V2 transfer and withdrawal endpoints |
|---|---|---|
| Standardized V2 values in this guide | Accepted and recommended | Accepted and recommended when released |
| Existing supported V1 values | Accepted for compatibility | Retained for compatibility when released |
V2 asset-operation endpoints are not yet released. Using a V2 enum value does not require switching to a V2 URL. Compatibility applies to request values; it does not change an endpoint's request fields, permissions or response format.
For example, for a Binance cross-margin account:
| Recommended value | Compatible V1 value |
|---|---|
MARGIN_CROSS | MARGIN |
Use the value for the specific exchange and account mode. Do not derive other legacy aliases by replacing underscores, hyphens or spaces, or by using an exchange's native wallet identifier.
Which field uses these values?
| Endpoint | Account-type fields |
|---|---|
| V1 Transfer | fromAccountType and toAccountType |
| V1 Withdraw | fromAccountType |
| V2 Transfer — not yet released | fromAccountType and toAccountType |
| V2 Withdrawal — not yet released | accountType |
For transfers, select each side independently. A source DMA account and a destination RapidX Portfolio use different kinds of account-type values.
| Account being selected | Meaning of the account-type field | Example |
|---|---|---|
| DMA exchange account | Wallet or account type within that exchange | Binance SPOT or MARGIN_CROSS |
| RapidX Portfolio | Exchange within the Portfolio | BINANCE, OKX or EDX |
| LTP Funding Account | Follow the endpoint's Funding Account rules; do not use a DMA enum to identify the LTP Funding Account | An exchange's FUNDING wallet is not the LTP Funding Account |
Required fields and permitted transfer or withdrawal routes are defined by each endpoint. An enum entry identifies an account type; it does not guarantee that every currency, network, direction or withdrawal route is available.
This guide is not a complete inventory of exchange wallets. An account type may still exist and hold assets even when LTP does not support API transfers for it. Being excluded from the supported transfer account types does not remove the account or its existing assets.
DMA account types by exchange
The Recommended value column contains the value to send. Account modes identify the account's existing configuration; they are not additional transfer or withdrawal request parameters. Mode codes and names are shown as configured and can differ between exchanges.
Account labels describe the wallets and are not parameter values. Exchange-native wallet codes are not the LTP OpenAPI enum.
Account mode describes how an exchange account manages balances, collateral and margin. Account type selects the wallet used for a transfer or withdrawal. The mode descriptions below explain the exchange's account structure; the recommended-value tables define LTP's supported account-type selections.
Binance
Account modes
| Mode in this guide | Meaning | Description |
|---|---|---|
CLASSIC | Standard account structure | Spot, Cross Margin, USDⓈ-M Futures and COIN-M Futures use separate wallets rather than a Portfolio Margin arrangement. |
PM_1, PM_2, PM_3 | Portfolio Margin configurations | Eligible assets across Cross Margin and Futures support margin requirements together. These three codes have the same supported transfer selections in the table below. |
Binance's public documentation explains Portfolio Margin and Portfolio Margin Pro, but does not establish a one-to-one mapping to the PM_1, PM_2 and PM_3 codes shown here. The numeric suffix is not an official version mapping in this guide.
Official references: Portfolio Margin overview, standard and Portfolio Margin modes, Portfolio Margin / Pro naming.
Supported account types
| Account mode | Recommended value | Account label |
|---|---|---|
CLASSIC, PM_1, PM_2, PM_3 | SPOT | Spot |
CLASSIC | MARGIN_CROSS | Cross Margin |
CLASSIC | U_MARGINED_FUTURES | USDⓈ-M Futures |
CLASSIC | C_MARGINED_FUTURES | Coin-M Futures |
PM_1, PM_2, PM_3 | MARGIN_CROSS | Portfolio Margin |
In Portfolio Margin mode, use MARGIN_CROSS for the Portfolio Margin wallet. The separate classic-mode futures account types are not separate transfer selections in these PM modes.
Binance's Funding wallet is not supported for transfers through LTP's API and is therefore not listed above. It can still hold assets; the transfer restriction does not remove those assets. Binance Funding is separate from the LTP Funding Account.
OKX
Account modes
These codes correspond to OKX's acctLv field.
| Mode in this guide | Official name | Description |
|---|---|---|
1 | Spot mode | Cash-funded spot trading rather than a cross-currency margin account. |
2 | Futures mode | Cross-margin positions using the same margin currency share that currency's margin balance; different margin currencies are managed separately. |
3 | Multi-currency margin | Eligible collateral currencies are valued in USD and jointly support cross-margin requirements. |
4 | Portfolio margin | Margin is assessed using portfolio risk and eligible position offsets, rather than only summing individual position requirements. |
Funding and Trading remain separate account-type selections in all four modes. Official references: account configuration and mode codes, Futures versus Multi-currency margin, Portfolio margin comparison.
Supported account types
| Account mode | Recommended value | Account label |
|---|---|---|
1, 2, 3, 4 | FUNDING | Funding |
1, 2, 3, 4 | TRADING | Trading |
Bybit
Account modes
| Mode in this guide | Official name | Description |
|---|---|---|
6 | Unified Trading Account 2.0 Pro | Bybit's unifiedMarginStatus=6. Spot and supported derivatives, including inverse contracts, are managed within the unified trading system. Margin sharing depends on the selected margin mode. |
UTA 2.0 Pro is an account-system version, not a synonym for Portfolio Margin. LTP currently supports mode 6 only. Official reference: Bybit account modes.
Supported account types
| Account mode | Recommended value | Account label |
|---|---|---|
6 | FUNDING | Funding |
6 | UNIFIED_2 | Unified Trading |
Gate
Account modes
| Mode in this guide | Official name | Description |
|---|---|---|
CLASSIC | Classic account / Classic Spot Mode | Spot and derivative wallets remain separately managed; there is no shared unified margin pool across them. |
single_currency | Single-Currency Margin Mode | USDT is the margin currency for the unified account; other assets do not form a shared multi-currency collateral pool. |
multi_currency | Multi-Currency Margin Mode | Eligible assets are valued in USD and used as shared collateral across supported products. |
portfolio | Portfolio Margin Mode | Portfolio risk calculations recognize eligible hedges within risk units when determining margin requirements. |
Coin-margined perpetual and delivery futures wallets remain outside the unified account's scope. Official references: API mode codes, margin-mode comparison, classic versus unified account scope.
Supported account types
| Account mode | Recommended value | Account label |
|---|---|---|
CLASSIC | SPOT | Spot |
CLASSIC | U_PERP_FUTURES | U Perp Futures |
CLASSIC | C_PERP_FUTURES | C Perp Futures |
CLASSIC, single_currency, multi_currency, portfolio | U_DELIVERY_FUTURES | U Delivery Futures |
single_currency, multi_currency, portfolio | TRADING | Trading |
single_currency, multi_currency, portfolio | C_PERP_FUTURES | BTC Perp Futures |
Bitfinex
CLASSIC is the label used here for Bitfinex's separate-wallet structure, not an additional mode to select on Bitfinex. The Exchange wallet is used for spot trading; Margin and Funding wallets have different purposes. Only the supported LTP transfer selection is listed below. Official reference: Bitfinex wallet types.
| Account mode | Recommended value | Account label |
|---|---|---|
CLASSIC | EXCHANGE | Exchange |
Bitget
Account modes
| Mode in this guide | Official name | Description |
|---|---|---|
classic | Classic account | Spot, margin and futures balances are managed in separate accounts. |
unified | Unified Trading Account | Spot and supported derivatives share a trading account. Collateral and margin treatment depend on the UTA margin mode. |
unified identifies the account system; it does not specify whether the account uses Bitget's Isolated, Basic or Advanced margin mode. Official references: Classic versus UTA, UTA account and margin modes.
Supported account types
| Account mode | Recommended value | Account label |
|---|---|---|
classic | SPOT | Spot |
classic | MARGIN_CROSS | Cross Margin |
classic | C_MARGINED_FUTURES | Coin-M Futures |
classic | U_MARGINED_FUTURES | U-M Futures |
classic | USDC_MARGINED_FUTURES | USDC-M Futures |
unified | FUNDING | Funding |
unified | TRADING | Trading |
Coinbase
CLASSIC is the label used here for the Coinbase Exchange spot-account configuration, not a Coinbase margin-mode code. Coinbase Exchange tracks balances by currency within a profile. Official reference: Coinbase Exchange accounts.
| Account mode | Recommended value | Account label |
|---|---|---|
CLASSIC | SPOT | Spot |
KuCoin
Account modes
| Mode in this guide | Official name | Description |
|---|---|---|
CLASSIC | Classic account | Spot, margin and futures use separately managed accounts and balances. |
UNIFIED | Unified Trading Account | Supported trading products share a collateral pool with cross-currency margin and combined risk management. Funding remains a separate wallet selection. |
Official references: Classic and Unified account comparison, Funding and trading account purposes.
Supported account types
| Account mode | Recommended value | Account label |
|---|---|---|
CLASSIC, UNIFIED | FUNDING | Funding |
CLASSIC | MARGIN_CROSS | Cross Margin |
CLASSIC | SPOT | Spot Trading |
CLASSIC | U_MARGINED_FUTURES | U-M Futures |
UNIFIED | TRADING | Unified Trading |
Deribit
Account modes
| Mode in this guide | Official name | Description |
|---|---|---|
segregated_sm | Segregated Standard Margin | Each settlement currency is managed separately. Individual position margin requirements are added within that currency. |
cross_sm | Cross Standard Margin | Individual position requirements are added, while eligible collateral assets can support requirements across currencies. |
segregated_pm | Segregated Portfolio Margin | Portfolio risk and eligible position offsets are assessed within each asset; collateral remains segregated by settlement currency. |
cross_pm | Cross Portfolio Margin | Portfolio margin is calculated within each asset, then combined in USD against shared collateral. Positions in different assets are not risk-netted against each other. |
Here, “segregated” means separation by settlement currency, not isolated margin for each individual position. All four modes use the same LTP TRADING selection. Official references: margin-model definitions, API margin-model codes.
Supported account types
| Account mode | Recommended value | Account label |
|---|---|---|
cross_pm, segregated_sm, cross_sm, segregated_pm | TRADING | Trading |
Phemex
CLASSIC identifies the separate Spot and Contract account structure used here. Funds in the Spot wallet and Contract trading accounts are managed separately. Official reference: Phemex Spot and Contract accounts.
| Account mode | Recommended value | Account label |
|---|---|---|
CLASSIC | SPOT | Spot |
CLASSIC | CONTRACT | Futures |
Hyperliquid
Account modes
| Mode in this guide | Meaning | Description |
|---|---|---|
CLASSIC | Separate-wallet configuration | LTP exposes separate Spot and perps-DEX transfer selections. Hyperliquid's Standard mode similarly separates spot, perps and DEX balances. |
UNIFIED | Unified account | Each asset has a shared balance for spot and cross-margin perps positions collateralized by that asset, including across applicable perps DEXs. |
Unified account is distinct from Hyperliquid's Portfolio Margin mode, which can combine eligible collateral assets. Hyperliquid's UI also uses “Classic” as a broader account-unification label; use the LTP account's mode and the selections below rather than inferring a mapping from that UI label alone. Official reference: Hyperliquid account abstraction modes.
Supported account types
| Account mode | Recommended value | Account label |
|---|---|---|
CLASSIC | SPOT | Spot |
CLASSIC | PERPS_PERP | Perps |
CLASSIC | PERPS_XYZ | Perps-XYZ |
UNIFIED | TRADING | Unified Trading |
RapidX Portfolio values
For a RapidX Portfolio, send the exchange where funds are held or should be credited, not a DMA wallet type:
| Value | Exchange within the Portfolio |
|---|---|
BINANCE | Binance |
OKX | OKX |
EDX | EDX |
For example, fromAccountType=BINANCE selects the Binance side of a RapidX Portfolio, whereas fromAccountType=MARGIN_CROSS selects a margin wallet in a Binance DMA account. The account ID and endpoint fields determine which kind of account is being operated on.
Compatibility example
These are account-type field excerpts, not complete transfer requests. For the same Binance classic DMA account, either excerpt selects Spot as the source and Cross Margin as the destination.
Recommended:
{
"fromAccountType": "SPOT",
"toAccountType": "MARGIN_CROSS"
}Compatible legacy form:
{
"fromAccountType": "SPOT",
"toAccountType": "MARGIN"
}Use the same recommended values for the withdrawal source field where that route is supported. Keep the endpoint's existing account identifiers, authorization and other required parameters unchanged.
Legacy V1 account-type reference
The tables below preserve the account-type descriptions previously shown on the V1 transfer and withdrawal pages. Existing supported V1 request values remain compatible; standardized V2 values above are recommended. These original tables include display labels and are not a complete list of exact request-value aliases.
Historical account-mode descriptions below do not establish current route support. For current supported account modes, use the tables above; Bybit currently supports mode 6 only.
V1 Transfer — original reference
| Exchange | Original V1 account-type description |
|---|---|
| Binance | Classic Account: Spot, Margin, USDT/C-M, Coin-M PM Account: Spot, Margin-PM For transfer of Margin-PM account, it may take approximately one hour due to processing times at the exchange. |
| OKX | Funding, Trading |
| Bybit | Classic Account: Spot, Funding, USDT-M, Coin-M PM Account: Funding, Trading, Coin-M |
| Kucoin | Classic Account: Funding, Trading, USDT/C-M, Coin-M,Cross PM Account: Unified Account, Funding |
| Gate | Classic Account: Spot, USDT-M Delivery Account, USDT-M Perpetual Account, BTC-M Perpetual Account PM Account: Unified Account, USDT-M Delivery Account, USDT-M Perpetual Account(Depends if you open the setting), BTC-M Perpetual Account Switching between Unified Account and Classic Account may take several minutes to half an hour to synchronize the balance. |
| Bitget | Classic Account: Spot, Margin, USDT-M, USDC-M, Coin-M PM Account: Unified Account, Funding |
| PHEMEX | Spot, USDT/C-M, Coin-M |
| LTP-Trading Portfolio | OKX, BINANCE |
V1 Withdrawal — original reference
| Exchange | Original V1 account-type description |
|---|---|
| Binance | Classic Account: Spot, Margin, USDT/C-M, Coin-M PM Account: Spot, Margin-PM For transfer of Margin-PM account, it may take approximately one hour due to processing times at the exchange. |
| OKX | Funding, Trading |
| Bybit | Classic Account: Spot, Funding, USDT-M, Coin-M PM Account: Funding, Trading, Coin-M |
| Kucoin | Classic Account: Funding, Trading, USDT/C-M, Coin-M,Cross PM Account: Unified Account, Funding, Cross |
| Gate | Classic Account: Spot, USDT-M Delivery Account, USDT-M Perpetual Account, BTC-M Perpetual Account PM Account: Unified Account, USDT-M Delivery Account, USDT-M Perpetual Account(Depends if you open the setting), BTC-M Perpetual Account Switching between Unified Account and Classic Account may take several minutes to half an hour to synchronize the balance. |
| Bitget | Classic Account: Spot, Margin, USDT-M, USDC-M, Coin-M PM Account: Unified Account, Funding |
| LTP - Trading Portfolio | BINANCE, OKX |
Updated about 6 hours ago