Pull cross-venue reference prices over a FIX 4.4 market-data session for crypto, forex, and metals, then feed them into
MetaTrader. Market data only.
Your trading system already speaks FIX. The strategy engine, order manager, and risk checks all parse tag=value messages over a persistent session, and bolting on a separate transport just for reference prices means another reconnect loop, another schema, and another thing to page someone about at 3 am. So the question is narrow and practical: how do you pull clean crypto, forex, and metals prices into a pipeline that already talks FIX, without standing a REST poller next to it?
SiftingIO exposes its aggregated market data over a FIX 4.4 session. One detail matters before anything else, because it shapes every design decision downstream: this is a market-data path, not an order-entry one. There is no order routing, no execution, no liquidity bridge. What comes down the wire is the same cross-venue consensus price the REST and WebSocket APIs serve, formatted as standard FIX market-data messages. The useful framing for a low-latency desk is a reference of record that sits above the execution feeds you already have, so you can sanity-check the quote a venue is printing against an independent consensus value.
The session lifecycle
The transport is TCP over TLS from IP-allowlisted source addresses, terminating at one of three cross-connect points: TY3 in Tokyo, NY4 in New York, and LD4 in London. Pick the one closest to where your engine runs. FIX 4.4 is the standard dialect, with FIX 5.0 SP2 available on request.
A session opens with a Logon (35=A) carrying your SenderCompID and the TargetCompID of SIFTINGIO. After that, the connection is kept alive with a Heartbeat (35=0) on a 30-second interval, and a TestRequest (35=1) prompts a heartbeat if the counterparty has gone quiet. Logout (35=5) closes it cleanly.
Subscribing is a MarketDataRequest (35=V). You set SubscriptionRequestType to a snapshot-plus-updates subscription, list your symbols using SiftingIO canonical codes, and the server answers with a MarketDataSnapshotFullRefresh (35=W) to seed the book, then a stream of MarketDataIncrementalRefresh (35=X) messages for every change after that. If you ask for something you cannot have, you get a MarketDataRequestReject (35=Y) instead. To discover what you can subscribe to, a SecurityList request (35=x) returns the tradable universe (35=y).
The price entries themselves ride in repeating groups keyed by MDEntryType (269): bid is 0, offer is 1, and trade is 2. Each entry carries MDEntryPx (270) for the price and MDEntrySize (271) for the size, with NoMDEntries (268) up to three per update. A minimal subscribe message for a crypto pair looks like this in pipe-delimited form:
8=FIX.4.4|35=V|49=YOUR_SENDER|56=SIFTINGIO|
262=req-btc-1|263=1|264=1|267=2|269=0|269=1|
146=1|55=BTCUSD|
That asks for bids and offers on BTCUSD as a live subscription. Symbols follow the canonical pair form you already use elsewhere on the platform: BTCUSD and ETHUSD for crypto, GBPUSD for forex, XAUUSD for metals.
Using it as a validation layer
The stronger use of an independent feed is not to drive execution from it, it is to catch the moment your execution venue is wrong. For fragmented and thin markets there often is no single true price, so a consensus median across multiple independent venues is frequently more correct than any one venue's print. The FIX session gives your low-latency path that consensus value, and a comparison against what your broker is quoting flags a stale, thin, or manipulated number before it reaches a risk decision.
The same consensus price is reachable over REST, which is handy for a backfill job or a slower out-of-band check that does not justify a FIX session of its own:
curl -H "X-API-Key: $SIFTING_KEY" \
"https://api.sifting.io/v1/last/quote/crypto/BTCUSD"
That returns the latest best bid and ask snapshot. REST auth is the X-API-Key header; the FIX side authenticates through your CompID pair and the IP allowlist instead. There is no Bearer token anywhere.
Wiring the feed into MetaTrader
A common destination for this feed is a MetaTrader 4 or 5 server that needs prices for Market Watch, charts, and indicators. SiftingIO supports that as a server-side market-data path, again with no execution or liquidity component. Your bridge runs a FIX initiator (QuickFIX or a compatible engine), allowlisted by IP, that maps SiftingIO canonical codes to your platform symbols and pushes bid and ask into the MT4 DataFeed API or the MT5 Gateway API, which then broadcasts to every client terminal. The full setup, including the BeginString=FIX.4.4 and TargetCompID=SIFTINGIO session config, is documented on the MetaTrader integration page.
Common pitfalls
Forex and metals carry no trade entries. Only crypto publishes MDEntryType 2; for GBPUSD or XAUUSD you will only ever see bid (0) and offer (1). A handler written against crypto that waits for a trade print to compute a price will sit silent forever on those symbols. Derive a mid from the bid and ask instead.
Do not expect a ResendRequest to replay missed ticks. For market data the server answers a gap with a SequenceReset-GapFill rather than re-sending stale prices, which is the correct behavior: a quote from two seconds ago is noise, not recovery. After a gap, resynchronize from the next MarketDataSnapshotFullRefresh rather than trying to reconstruct what you missed.
Watch the source IP. The allowlist is matched on the connecting address, so a session behind NAT, a load balancer, or an ephemeral cloud egress IP will fail Logon with no useful application-level message. Pin static source IPs and confirm them before debugging anything higher in the stack. Separately, a MarketDataRequestReject (35=Y) on a symbol you believe is valid is usually an entitlement limit, not a bad symbol: concurrent sessions and symbols-per-session are capped by plan, and FIX access itself sits behind a FIX entitlement.
One last framing note that keeps you on the right side of the data: the value on the wire is a synthetic reference price, not an official exchange-of-record print and not executable depth. It is built to be resistant to a minority of bad feeds, not to survive a majority of venues all erring the same way, and it is a reference rather than a sub-millisecond execution feed. Treat it as the cross-check above your trading stack, and it earns its place in a fast pipeline.