post
https://api.liquiditytech.com/api/v1/userWithdrawRecord/apply
Support withdrawal of tokens from Funding Account, Exchange Account and Trading Porfolio.
Recent Requests
Log in to see full request history
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Loading…
TipsApplies to both user and trading portfolio's API Key. Permission: WITHDRAW.
Request
| Field name | Type | Necessary | Remarks |
|---|---|---|---|
| accountId | Long | Y | Trade account ID or Portfolio ID |
| fromAccountType | String | Conditional | Source account type. Required for a RapidX Trading Portfolio: BINANCE, OKX or EDX. For a DMA exchange account, choose the standardized V2 value for its exchange and account mode. Standardized V2 values are recommended on this V1 endpoint; existing supported V1 values remain compatible. See Account Types. |
| currency | String | Y | Currency |
| network | String | Y | Network |
| address | String | Y | Address |
| memo | String | N | Check if the receiving platform requires you to include a tag/memo. If required, ensure the tag/memo is correct to avoid losing your assets. |
| amount | string | Y | Quantity(minimum amount : 0.01 BTC ; 0.1 ETH ; 100 USDT ) |
| addressTag | String | N | Address tag is the label you entered for your address at LTP, which is different than memo. |
| clientOrderId | String | N | The unique user-defined id |
| loanTrans | Boolean | N | Only the trading account from OKX exchange supports this feature. Other accounts don't support this feature. |
| rapidTransfer | Boolean | Conditional | No longer in effect. Withdrawals are outside the scope of Rapid Transfer as of the 26 Aug 25th release. The field is still accepted so existing integrations keep working, but setting it to true changes nothing — the withdrawal goes on chain either way. See the Rapid Transfer guide. |
Response
| Field name | Type | Remarks |
|---|---|---|
| data | Long | Withdraw id |
Details
1. API Key
| API Key | Permission |
|---|---|
| Primary user’s API Key | Supports withdrawals from all Trading Portfolios under the primary user. |
| Trading Portfolio API Key: | Can only be used to withdraw from the Trading Portfolio associated with that API key. |
2. Account Type
See Account Types for the shared exchange-by-mode enum reference. Use the standardized V2 values for new integrations, including requests to this V1 endpoint. Existing supported V1 values remain compatible; for example, Binance MARGIN is accepted alongside MARGIN_CROSS.
For a DMA account, select the wallet type for its exchange and account mode. For a RapidX Portfolio, select BINANCE, OKX or EDX. Follow this endpoint’s rules for an LTP Funding Account. Enum compatibility does not change permissions or available routes.
Operational notes:
- Transfers involving Binance Portfolio Margin may take approximately one hour due to exchange processing.
- Switching a Gate account between Unified and Classic modes may take several minutes to half an hour to synchronize balances.
3. Network
- This field will only take effect in cross-exchange transfers.
- If you want to select a specific network to transfer, please select according to the following fields.
| Network Field |
|---|
| TRC20, BTC, ERC20, BSC, APT, ADA, ALGO, AVAXC, DOGE, EGLD, ETC, IOTA, KSM, NEO3, ONT, QTUM, THETA, XMR, ZEC, DOT, FTM, MATIC, SOL, OPTIMISM, ARBITRUM, RON, LTC, EOS, XRP, BOBA, FIL, CFX, BCH, NEAR |