Broker API HubMenu

Capital.com vs OANDA API

The same fields from the Capital.com record and the OANDA 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 OANDA, field by field

FieldCapital.comOANDA
KindBroker with its own APIBroker with its own API
API familyREST, WebSocketREST (v20), HTTP streaming
How you get accessEnable 2FA, then Settings > API integrations > Generate new key, with a custom key password.Capital.com Public APIchecked Account Management Portal > My Services > Manage API Access, accept licence, generate personal access token.OANDA v20 Introductionchecked
Who can use itAny Capital.com account (demo or live) with 2FA enabled. Regional limits not published.Capital.com Public APIchecked Needs a v20 account; available in all divisions except OANDA Global Markets and OANDA TMS Brokers S.A.OANDA v20 Introductionchecked
DemoYes: separate demo base URL.Capital.com Public APIchecked Yes: fxTrade Practice environment with its own token.OANDA Development Guidechecked
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 Bearer personal access token, generated in the Account Management Portal after accepting the API licence.Introduction, OANDA v20 REST APIchecked
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 HTTP chunked transfer encoding carrying JSON objects, not WebSocket. The development guide states at most 20 active streams, with requests above that rejected, and no more than 2 new connections a second. The best practices page advises no more than 100 requests a second on an established connection. Sources: https://developer.oanda.com/rest-live-v20/development-guide/ and https://developer.oanda.com/rest-live-v20/best-practices/, both read 23 September 2026, development guide re-read 24 September 2026.OANDA Development Guidechecked
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 Historical pricing back to 2005, on the introduction page. Candles: at most 5,000 per request, 500 by default, on the pricing endpoints page. Transactions: at most 365 days per request, in pages of up to 1,000.OANDA v20: Introductionchecked
Limits
  • Headline limit: 120/s per IP address, HTTP 429 above it. ipdeveloper.oanda.comchecked
Endpoints documented here3633
Error codes decoded here24242
Official documentationopen-api.capital.comdeveloper.oanda.com

Go deeper on each side

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