Instrument definition
XAU/USD spot, a dated gold futures contract and a broker's gold CFD need distinct mappings. Confirm quotation units and precision with the counterparty; a familiar GOLD label does not establish contract equivalence.
Market data · deployment planning
Gold FIX Feed
Identify the gold instrument and its units before mapping prices into a FIX market-data session.
Interface acceptance
Validate the agreed FIX entry types and the handling of closed sessions, subscription errors and stale observations. Keep the trading server's symbol configuration aligned with the instrument specification rather than changing it implicitly from feed messages.
Requirements to confirm
- Spot, futures or CFD scope
- Quotation unit and currency
- FIX entry-type mapping
- Server symbol acceptance test
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.
Integration brief
Gold FIX Feed: what to agree before connecting
| 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. |
Use the counterparty specification
A FIX delivery plan for precious metals 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.
What to test
- Exercise logon, disconnect and recovery in a test environment.
- Compare the agreed snapshot with subsequent incremental updates.
- Record rejected symbols and the reason supplied by the counterparty.