Match-Trader vs TradeLocker API
The same fields from the Match-Trader Platform API record and the TradeLocker API record, side by side. No winner is picked: which one suits you depends on what you are building.
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.
- Match-Trader Platform API 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 17 endpoints for Match-Trader Platform API and 23 endpoints for TradeLocker API. That counts what has been documented here, not what each API offers.
- This site has decoded 3 error codes for Match-Trader Platform API and 5 error codes for TradeLocker API.
- The limits register holds no limit records for Match-Trader Platform API and no limit records for TradeLocker API. Each limit record carries its own scope.
- The Match-Trader Platform API record holds a demo claim, marked unverified. 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: 1 in the Match-Trader Platform API record and 1 in the TradeLocker API record. Each is labelled where it appears.
- A quickstart is built here for neither yet.
Match-Trader Platform API and TradeLocker API, field by field
| Field | Match-Trader Platform API | TradeLocker API |
|---|---|---|
| Kind | Platform API, offered by many brokers | Platform API, offered by many brokers |
| API family | REST, WebSocket (STOMP) | REST, Streams API (Socket.IO WebSocket), Python package |
| How you get access | Log in with your Match-Trader credentials and broker ID; availability appears to be controlled by the broker.Platform APIchecked | Use your TradeLocker login (email, password, server) against the public REST API; no separate app registration found.TradeLocker API connectivitychecked |
| Who can use it | Traders with an account at a broker that runs Match-Trader. Match-Trade's Platform API page says the API is designed primarily for traders, and that a broker on a server licence can selectively disable its functionality, so whether it works for you is the broker's decision. The page also says Match-Trader is not provided to individuals directly.Match-Trader Platform APIchecked | TradeLocker users only, via a broker or prop firm that offers TradeLocker.Getting Started with TradeLocker Public APIchecked |
| Demo | Unverified. Match-Trade's Platform API page, re-read 12 Oct 2026, links a Try demo platform at demo.match-trader.com. That is a demo of the platform, and neither that page nor the documentation index says whether the API can be used against it or gives a demo API address.UnverifiedMatch-Trader Platform APIchecked | Yes: separate demo environment at demo.tradelocker.com.Getting Started with TradeLocker Public APIchecked |
| Authentication | POST email, password and brokerId to /manager/co-login, or manager/login/co/with-token for a one time token. The co-auth cookie has Max-Age 3600 seconds and the refresh cookie rt has Max-Age 31536000 seconds, Secure and HttpOnly; refresh at manager/refresh-token with no body. Trading calls need the Auth-trading-api header taken from tradingAccounts plus the co-auth cookie.Match-Trader Platform API PDF (2024)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 | Yes: WebSocket with STOMP for real-time market data and account updates.Platform APIchecked | 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 | Get candles and closed positions endpoints exist; no depth or per request limit found in public docs.Match-Trade Platform API docs (Theneo)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 | 17 | 23 |
| Error codes decoded here | 3 | 5 |
| Official documentation | docs.match-trade.com | public-api.tradelocker.com |
Go deeper on each side
Match-Trader Platform API
- Match-Trader API page, the full record
- No Match-Trader API quickstart is built here yet
- Match-Trader API limits, in the table above: none recorded
- Match-Trader API error codes, each with its fix
- Match-Trader 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.