An overview of LTP API and Exchange API — what they control, who can use them, and how permissions work.
Overview
LTP provides two distinct categories of API:
| Category | What it controls |
|---|---|
| LTP API | Fund transfers, withdrawals, and RapidX trading — all within the LTP platform |
| Exchange API | Trading operations directly on an exchange, scoped to a specific DMA sub-account |
Both are managed in Personal Center → API Management.
LTP API
The Main Account and Main Portfolio are the Same API
When you log in to LTP with your email, that identity is also your RapidX Main Portfolio. The API key you create for your main account is therefore both:
- A trading API — place and manage orders on RapidX on behalf of the Main Portfolio
- A user-level API — transfer and withdraw across all LTP account types
The right to move assets across accounts comes from the LTP main account level, not from any individual portfolio. Even when using the same API key to trade, it is the main account identity that authorises cross-account transfers.
Sub Portfolio API
Each sub portfolio has its own API, scoped exclusively to that portfolio. A sub portfolio API can:
- Trade on RapidX on behalf of that sub portfolio
- Transfer and withdraw within that sub portfolio's own balance
A sub portfolio API cannot move assets between accounts — that requires the main account API.
Permissions
When creating an LTP API key, you can assign one or more of the following permissions:
| Permission | Description |
|---|---|
| Read | View account balances, positions, and order history |
| Transfer | Move assets between portfolios and sub-accounts |
| Withdraw | Withdraw assets to an external address |
| Trade (RapidX) | Place and manage orders on RapidX |
API Scope by Account Type
| API Level | Who can create | Capabilities |
|---|---|---|
| User-level (Master user) | Master user only | This is the Main Portfolio API. Trade on RapidX (Main Portfolio) + transfer and withdraw across all LTP account types |
| User-level (Sub-user) | Sub-user | Transfer and withdraw across all resources assigned to that sub-user |
| Portfolio-level | Master user, or the sub-user assigned to that portfolio | Trade, transfer, and withdraw scoped to that specific portfolio |
Sub-user API
Sub-users do not have a Main Portfolio, but they do have their own user-level API. See Accounts for details on sub-users and how resources are assigned. Here is how it works:
- A sub-user can create user-level API keys that cover all resources assigned to them — transferring and withdrawing across any of their assigned DMA sub-accounts and portfolios
- For each assigned sub portfolio, a sub-user can also create multiple portfolio-level API keys, each scoped to that portfolio
Withdrawal whitelist: Withdrawals are controlled through an address whitelist managed by the master user. The master user adds addresses to the whitelist and then assigns specific addresses to sub-users. A sub-user can only withdraw to addresses that have been explicitly assigned to them.
Exchange API
Exchange APIs are exchange-native keys that LTP creates on the exchange on your behalf and assigns to your DMA sub-account. They are surfaced in API Management so you can view and manage them in one place.
Exchange APIs operate entirely at the exchange level:
- They control trading on the exchange for the linked DMA sub-account
- They cannot perform LTP-level operations such as transfers between sub-accounts or withdrawals through LTP
To transfer assets between DMA sub-accounts, or between a DMA sub-account and other LTP accounts, you must use an LTP API key (main account or sub-account level). Exchange-native API keys do not have access to LTP's transfer system.