eToro vs OANDA API
The same fields from the eToro record and the OANDA 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.
- eToro is recorded as a broker with an API of its own. OANDA is recorded as a broker with an API of its own.
- This site documents 51 endpoints for eToro and 33 endpoints for OANDA. That counts what has been documented here, not what each API offers.
- This site has decoded 16 error codes for eToro and 242 error codes for OANDA.
- The limits register holds 1 limit record for eToro and 1 limit record for OANDA. Each limit record carries its own scope.
- The eToro record holds a demo claim, verified at its source. The OANDA 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.
eToro and OANDA, field by field
| Field | eToro | OANDA |
|---|---|---|
| Kind | Broker with its own API | Broker with its own API |
| API family | REST, WebSocket, OAuth 2.0 SSO (partners) | REST (v20), HTTP streaming |
| How you get access | Settings > Trading > API Key Management > Create New Key; choose Read or Write, optional IP whitelist and expiry.eToro API portal: authenticationchecked | Account Management Portal > My Services > Manage API Access, accept licence, generate personal access token.OANDA v20 Introductionchecked |
| Who can use it | Verified eToro account required. Regional availability not published on pages opened.eToro API Portalchecked | Needs a v20 account; available in all divisions except OANDA Global Markets and OANDA TMS Brokers S.A.OANDA v20 Introductionchecked |
| Demo | Yes: the environment is bound to the key when it is created, Demo or Real, and each key supports one environment only.eToro Builders FAQchecked | Yes: fxTrade Practice environment with its own token.OANDA Development Guidechecked |
| Authentication | Headers x-api-key, x-user-key and x-request-id on every request, or an OAuth 2.0 bearer token instead of the key headers. eToro now states the exclusivity itself rather than leaving it to be inferred: a request presenting both is rejected.eToro API portal: authenticationchecked | Bearer personal access token, generated in the Account Management Portal after accepting the API licence.Introduction, OANDA v20 REST APIchecked |
| Streaming | WebSocket at wss://ws.etoro.com/ws, described by an AsyncAPI 3.0 document that eToro publishes. Instrument topics need no authentication; the private topic needs an Authenticate message first, which carries the user key and API key inside its data object over the open socket, never as a header. A Subscribe message lists topics such as instrument:<instrumentId> or private, with an optional snapshot flag. The AsyncAPI document, the Topics page and the example code agree on that shape. The server sends a single binary frame from time to time as a heartbeat. No connection or subscription limit is given and no reconnection or replay behaviour is described.eToro WebSocket API, AsyncAPI documentchecked | 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 depth | Candles: max 1,000 per request, one minute to one week. Trading history: lookback under 1 year per request; split longer ranges.eToro API: Get instrument candle historychecked | 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 |
|
|
| Endpoints documented here | 51 | 33 |
| Error codes decoded here | 16 | 242 |
| Official documentation | api-portal.etoro.com | developer.oanda.com |
Go deeper on each side
eToro
- eToro API page, the full record
- eToro API quickstart, credentials to a first call
- eToro API limits, in the table above
- eToro API error codes, each with its fix
- eToro API endpoints, each with its source
- Get your eToro trade history into a spreadsheet
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
All comparisons. New to this? Getting started with API trading.