OANDA vs Saxo API
The same fields from the OANDA 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.
- OANDA 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 33 endpoints for OANDA and 68 endpoints for Saxo OpenAPI. That counts what has been documented here, not what each API offers.
- This site has decoded 242 error codes for OANDA and 143 error codes for Saxo OpenAPI.
- The limits register holds 1 limit record for OANDA and 1 limit record for Saxo OpenAPI. Each limit record carries its own scope.
- The OANDA 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.
OANDA and Saxo OpenAPI, field by field
| Field | OANDA | Saxo OpenAPI |
|---|---|---|
| Kind | Broker with its own API | Broker with its own API |
| API family | REST (v20), HTTP streaming | REST, WebSocket streaming |
| How you get access | Account Management Portal > My Services > Manage API Access, accept licence, generate personal access token.OANDA v20 Introductionchecked | 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 | Needs a v20 account; available in all divisions except OANDA Global Markets and OANDA TMS Brokers S.A.OANDA v20 Introductionchecked | 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: fxTrade Practice environment with its own token.OANDA Development Guidechecked | Yes: SIM environment; 24 hour portal tokens work in SIM only.Saxo Environmentschecked |
| Authentication | Bearer personal access token, generated in the Account Management Portal after accepting the API licence.Introduction, OANDA v20 REST 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 | 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 | 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 | 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 | 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 | 33 | 68 |
| Error codes decoded here | 242 | 143 |
| Official documentation | developer.oanda.com | developer.saxo |
Go deeper on each side
OANDA
- OANDA API page, the full record
- OANDA API quickstart, credentials to a first call
- OANDA API limits, in the table above
- OANDA API error codes, each with its fix
- OANDA API endpoints, each with its source
- Get your OANDA trade history into a spreadsheet
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.