Broker API HubMenu

FXCM vs OANDA API

The same fields from the FXCM 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.

FXCM and OANDA, field by field

FieldFXCMOANDA
KindBroker with its own APIBroker with its own API
API familyFIX, Java API, ForexConnectREST (v20), HTTP streaming
How you get accessFree SDKs from FXCM GitHub; sign the EULA and apply for a demo account. Support at api@fxcm.com.GitHub fxcm/ForexConnectAPIchecked Account Management Portal > My Services > Manage API Access, accept licence, generate personal access token.OANDA v20 Introductionchecked
Who can use itTrading Station account. FIX needs a minimum of 5,000 pounds or dollars. UK page dated 25 Jun 2025.FXCM API Tradingchecked Needs a v20 account; available in all divisions except OANDA Global Markets and OANDA TMS Brokers S.A.OANDA v20 Introductionchecked
DemoYes: ForexConnect connects to demo and real Trading Station accounts.GitHub fxcm/ForexConnectAPIchecked Yes: fxTrade Practice environment with its own token.OANDA Development Guidechecked
AuthenticationFIX, the Java API and ForexConnect only. No REST API is listed on FXCM's current API pages, so the legacy REST token flow this site described is recorded as no longer listed rather than retired.FXCM Socket REST API specchecked Bearer personal access token, generated in the Account Management Portal after accepting the API licence.Introduction, OANDA v20 REST APIchecked
StreamingForexConnect pushes live prices; the retired legacy REST API streamed over Socket.IO.FXCM Socket REST API specchecked 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: up to 10,000 per request with optional from and to. Depth of history and a trade history endpoint not documented.FXCM Socket REST API specschecked 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
LimitsNone recorded
  • Headline limit: 120/s per IP address, HTTP 429 above it. ipdeveloper.oanda.comchecked
Endpoints documented hereNone yet33
Error codes decoded hereNone yet242
Official documentationfxcm.comdeveloper.oanda.com

Go deeper on each side

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