DXtrade vs TradeLocker API
The same fields from the DXtrade APIs record and the TradeLocker API record, side by side. No winner is picked: which one suits you depends on what you are building.
Independent and unofficialNewest check
Risk warning: CFDs and spread bets are complex instruments and come with a high risk of losing money rapidly due to leverage. You can lose money on these products, and each provider publishes its own loss figure under FCA rules. You should consider whether you understand how they work and whether you can afford to take the high risk of losing your money. Automated and API trading can amplify losses through bugs, connectivity failures and runaway orders.
What the two records show
Differences you can see in the records themselves. These are counts of what this site holds, not a verdict on either API.
- DXtrade APIs is a platform API, offered through the brokers that carry the platform. TradeLocker API is a platform API, offered through the brokers that carry the platform.
- This site documents 21 endpoints for DXtrade APIs and 23 endpoints for TradeLocker API. That counts what has been documented here, not what each API offers.
- This site has decoded 79 error codes for DXtrade APIs and 5 error codes for TradeLocker API.
- The limits register holds no limit records for DXtrade APIs and no limit records for TradeLocker API. Each limit record carries its own scope.
- The DXtrade APIs record holds a demo claim, verified at its source. The TradeLocker API record holds a demo claim, verified at its source. The wording of each is in the Demo row below.
- Claims marked unverified or as sources conflicting: 3 in the DXtrade APIs record and 1 in the TradeLocker API record. Each is labelled where it appears.
- A quickstart is built here for neither yet.
DXtrade APIs and TradeLocker API, field by field
| Field | DXtrade APIs | TradeLocker API |
|---|---|---|
| Kind | Platform API, offered by many brokers | Platform API, offered by many brokers |
| API family | REST, WebSocket (Push API) | REST, Streams API (Socket.IO WebSocket), Python package |
| How you get access | Client-side API exists, but you must go through your broker or prop firm, which controls permitted IPs.Traders' FAQchecked | Use your TradeLocker login (email, password, server) against the public REST API; no separate app registration found.TradeLocker API connectivitychecked |
| Who can use it | Broker or prop firm dependent; Devexperts does not deal with traders directly.Traders' FAQchecked | TradeLocker users only, via a broker or prop firm that offers TradeLocker.Getting Started with TradeLocker Public APIchecked |
| Demo | No trader demo from Devexperts: the demo on the DXtrade website is for brokers and prop firms to trial the software. Ask your broker for a demo account.DXtrade: Traders FAQchecked | Yes: separate demo environment at demo.tradelocker.com.Getting Started with TradeLocker Public APIchecked |
| Authentication | Unverified. The DXtrade developer portal at demo.dx.trade/developers returned only a page title without scripts on 12 Oct 2026, as it did in September, so the authentication scheme could not be read. Devexperts' APIs page links to that portal and states nothing itself.UnverifiedDXtrade developer portal (content did not render)checked | POST email, password and server to /auth/jwt/token; send the JWT as Bearer token; refresh tokens issued. /trade/* routes also need the accNum header (not the accountId).Getting Started with TradeLocker Public APIchecked |
| Streaming | Push API over WebSockets for account and market data updates.Devexperts blog: DXtrade API suitechecked | Unverified. TradeLocker's public API documentation, re-read 12 Oct 2026, describes a request and response REST API only, and its index of pages lists no streaming page. The record's API family names a Streams API from an earlier reading that could not be confirmed on a page that opens today.UnverifiedTradeLocker public API, getting startedchecked |
| History depth | Unverified. The DXtrade developer portal returned only a page title without scripts on 12 Oct 2026, so candle and trade history depth could not be read.UnverifiedDXtrade developer portal (content did not render)checked | /trade/history by resolution (1m to 1M) and from/to; max rows per request and orders history rows come from /trade/config.TradeLocker Public API docschecked |
| Limits | None recorded | None recorded |
| Endpoints documented here | 21 | 23 |
| Error codes decoded here | 79 | 5 |
| Official documentation | demo.dx.trade | public-api.tradelocker.com |
Go deeper on each side
DXtrade APIs
- DXtrade API page, the full record
- No DXtrade API quickstart is built here yet
- DXtrade API limits, in the table above: none recorded
- DXtrade API error codes, each with its fix
- DXtrade API endpoints, each with its source
TradeLocker API
- TradeLocker API page, the full record
- No TradeLocker API quickstart is built here yet
- TradeLocker API limits, in the table above: none recorded
- TradeLocker API error codes, each with its fix
- TradeLocker API endpoints, each with its source
All comparisons. New to this? Getting started with API trading.