Session versus instrument state
A connected FIX session does not establish that every CFD subscription is healthy. Monitor requested symbols, subscription responses and the age of each bid/ask independently from session heartbeats.
Scope a FIX market-data session for CFDs around the instrument dictionary and message behavior agreed by both parties.
A connected FIX session does not establish that every CFD subscription is healthy. Monitor requested symbols, subscription responses and the age of each bid/ask independently from session heartbeats.
Confirm the FIX version, supported messages, instrument identifiers and entry types with the counterparty. Treat snapshot and incremental handling as negotiated interface behavior; do not infer it from the word FIX alone.
Bring the proposed instrument list, source documentation and consumer workflow to a technical discussion. The agreed integration specification defines coverage, fields, usage permissions and acceptance tests.
| Session agreement | Confirm the FIX version, identifiers, heartbeat policy and recovery procedure with the counterparty. |
|---|---|
| Market-data scope | Agree requested instruments, entry types, depth if applicable and update behaviour. |
| Instrument model | Map source identifiers, price precision, timestamps and required metadata. |
| Operational recovery | Test session reconnects and the treatment of application state after recovery. |
A FIX delivery plan for your instrument universe must define the agreed version, session rules and market-data messages. Confirm snapshot and incremental semantics with the actual counterparty. Transport connectivity alone does not establish a complete, usable instrument state.