Starting with version 2026.6.0, the TsgcWSAPI_FXCM component and the underlying sgcWebSocket_API_FXCM unit are no longer part of the sgcWebSockets package. The removal applies to both the Delphi and the .NET editions, and also covers the matching design-time bitmap, the Demos\05.Crypto\07.FXCM sample project and the API documentation pages.
Why It Was Removed
FXCM has deprecated its public trading API. The ForexConnect, REST and streaming endpoints that TsgcWSAPI_FXCM connected to are no longer offered for third-party integrations — the broker now directs retail clients to third-party platforms such as MetaTrader 4, TradingView and its own branded apps. There is no successor endpoint that a drop-in component could target.
Keeping the component in the package would only ship a non-functional client: every connection attempt would fail at the transport layer, regardless of credentials. Removing it removes confusion and shrinks the build surface.
Migration Path
Two replacement components are already shipping, both introduced in sgcWebSockets 2026.5.0:
TsgcWSAPI_Forex is the direct functional replacement for retail forex trading. It implements the Forex.com REST and streaming protocol with the same one-component pattern TsgcWSAPI_FXCM used: log in, subscribe to market watch quotes, place orders, query positions and trade history.
uses
sgcWebSocket_API_Forex;
var
oForex: TsgcWSAPI_Forex;
begin
oForex := TsgcWSAPI_Forex.Create(nil);
try
oForex.Forex.User := 'your-user';
oForex.Forex.Password := 'your-password';
oForex.Forex.AppKey := 'your-app-key';
oForex.Active := True;
oForex.SubscribeMarketData('EUR/USD');
finally
oForex.Free;
end;
end;If your application targets a Lightstreamer-based broker feed in general — Forex.com, IG Markets and others all expose Lightstreamer TLCP 2.5 endpoints — the new TsgcWSPClient_Lightstreamer component is the lower-level option. It handles create_session, bind_session, subscribe / unsubscribe control messages, plus the LOOP auto-rebind and subscription replay after reconnect, so you can point it at any compliant server.
What Stays the Same
Every other crypto and forex exchange client in the package is unaffected. The 2026.6 build still ships TsgcWSAPI_Binance, Binance_Futures, Bitfinex, Bitget, Bitmex, Bitstamp, Bybit, Cex, CexPlus, Coinbase, Huobi, Kraken, Kraken_Futures, Kucoin, Kucoin_Futures, MEXC, MEXC_Futures, OKX, ThreeCommas, XTB, Forex and Deribit. No other API endpoints have changed.
Upgrading
The component removal is a breaking change only for projects that link the sgcWebSocket_API_FXCM unit explicitly or drop the TsgcWSAPI_FXCM component on a form. If your project does either, replace it with TsgcWSAPI_Forex (or TsgcWSPClient_Lightstreamer for a generic Lightstreamer client) before recompiling against 2026.6.
Questions, feedback or migration help? Get in touch — you will get a reply from the people who wrote the code.