Broker API HubMenu

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.

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 and Saxo OpenAPI, field by field

FieldCapital.comSaxo OpenAPI
KindBroker with its own APIBroker with its own API
API familyREST, WebSocketREST, WebSocket streaming
How you get accessEnable 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 itAny 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
DemoYes: separate demo base URL.Capital.com Public APIchecked Yes: SIM environment; 24 hour portal tokens work in SIM only.Saxo Environmentschecked
AuthenticationPOST /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
StreamingWebSocket 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 depthCandles: 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
  • Headline limit: 120/min per session, per service group. sessiondeveloper.saxochecked
Endpoints documented here3668
Error codes decoded here24143
Official documentationopen-api.capital.comdeveloper.saxo

Go deeper on each side

All comparisons. New to this? Getting started with API trading.