Capital.com vs Saxo API
The same fields from the Capital.com record and the Saxo OpenAPI 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.
- Capital.com is recorded as a broker with an API of its own. Saxo OpenAPI is recorded as a broker with an API of its own.
- This site documents 36 endpoints for Capital.com and 68 endpoints for Saxo OpenAPI. That counts what has been documented here, not what each API offers.
- This site has decoded 24 error codes for Capital.com and 143 error codes for Saxo OpenAPI.
- The limits register holds 1 limit record for Capital.com and 1 limit record for Saxo OpenAPI. Each limit record carries its own scope.
- The Capital.com record holds a demo claim, verified at its source. The Saxo OpenAPI record holds a demo claim, verified at its source. The wording of each is in the Demo row below.
- A quickstart is built here for both.
Capital.com and Saxo OpenAPI, field by field
| Field | Capital.com | Saxo OpenAPI |
|---|---|---|
| Kind | Broker with its own API | Broker with its own API |
| API family | REST, WebSocket | REST, WebSocket streaming |
| How you get access | Enable 2FA, then Settings > API integrations > Generate new key, with a custom key password.Capital.com Public APIchecked | Create a developer portal account for SIM (24 hour token or registered app); apply for live app credentials after testing.Saxo OpenAPI Learnchecked |
| Who can use it | Any Capital.com account (demo or live) with 2FA enabled. Regional limits not published.Capital.com Public APIchecked | Direct retail and professional clients may use it for personal use; a live account must be funded before creating a live app. The approval criteria for a retail live environment are unverified: the environments and security pages read on 19 Sep 2026 say live requires permission and testing before deployment but do not state what is required.Saxo Support: personal usechecked |
| Demo | Yes: separate demo base URL.Capital.com Public APIchecked | Yes: SIM environment; 24 hour portal tokens work in SIM only.Saxo Environmentschecked |
| 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 | OAuth 2.0 authorization code (with or without PKCE); app key and secret for live. Refresh tokens rotate: each is invalidated on use and replaced. Certificate-based auth is for select partners only, not retail.Saxo OpenAPI Learnchecked |
| 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 | WebSocket streaming (SIM and live hosts). The connection allowance and the instrument cap are unverified as of 20 Sep 2026: the streaming pages no longer publish either figure and say only that the number of WebSocket connections depends on the throttling profile assigned to the application.Saxo Environmentschecked |
| 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 | Chart samples max 1,200 per request; some FX data back to 2002. Trades report takes FromDate and ToDate with no stated limit.Saxo OpenAPI Support: How many samples can be returned at a time?checked |
| Limits |
|
|
| Endpoints documented here | 36 | 68 |
| Error codes decoded here | 24 | 143 |
| Official documentation | open-api.capital.com | developer.saxo |
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
Saxo OpenAPI
- Saxo API page, the full record
- Saxo API quickstart, credentials to a first call
- Saxo API limits, in the table above
- Saxo API error codes, each with its fix
- Saxo API endpoints, each with its source
All comparisons. New to this? Getting started with API trading.