Capital.com vs TradeLocker API
The same fields from the Capital.com 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.
- Capital.com is recorded as a broker with an API of its own. TradeLocker API is a platform API, offered through the brokers that carry the platform.
- This site documents 36 endpoints for Capital.com and 23 endpoints for TradeLocker API. That counts what has been documented here, not what each API offers.
- This site has decoded 24 error codes for Capital.com and 5 error codes for TradeLocker API.
- The limits register holds 1 limit record for Capital.com and no limit records for TradeLocker API. Each limit record carries its own scope.
- The Capital.com 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: 0 in the Capital.com record and 1 in the TradeLocker API record. Each is labelled where it appears.
- A quickstart is built here for Capital.com only.
Capital.com and TradeLocker API, field by field
| Field | Capital.com | TradeLocker API |
|---|---|---|
| Kind | Broker with its own API | Platform API, offered by many brokers |
| API family | REST, WebSocket | REST, Streams API (Socket.IO WebSocket), Python package |
| How you get access | Enable 2FA, then Settings > API integrations > Generate new key, with a custom key password.Capital.com Public 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 | Any Capital.com account (demo or live) with 2FA enabled. Regional limits not published.Capital.com Public APIchecked | TradeLocker users only, via a broker or prop firm that offers TradeLocker.Getting Started with TradeLocker Public APIchecked |
| Demo | Yes: separate demo base URL.Capital.com Public APIchecked | Yes: separate demo environment at demo.tradelocker.com.Getting Started with TradeLocker Public APIchecked |
| Authentication | POST /session with the X-CAP-API-KEY header plus login credentials returns CST and X-SECURITY-TOKEN, sent on later calls. The session expires after 10 minutes of inactivity.Capital.com Public APIchecked | 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 | WebSocket wss://api-streaming-capital.backend-capital.com/connect, maximum of 40 epics per subscription; the session lasts 10 minutes and is kept alive with ping.Capital.com Public 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 | Candles: max 1,000 per request (default 10), MINUTE to WEEK. Activity history: max 1 day per from/to call. Transactions default to last 10 minutes.Capital.com API referencechecked | /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 |
| Endpoints documented here | 36 | 23 |
| Error codes decoded here | 24 | 5 |
| Official documentation | open-api.capital.com | public-api.tradelocker.com |
Go deeper on each side
Capital.com
- Capital.com API page, the full record
- Capital.com API quickstart, credentials to a first call
- Capital.com API limits, in the table above
- Capital.com API error codes, each with its fix
- Capital.com API endpoints, each with its source
- Get your Capital.com trade history into a spreadsheet
- Capital.com API with Python
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.