Subscription detail
Specify whether a subscription is for a spot reference, a dated contract or a broker CFD. Include the normalized identifier in each update so a client cannot confuse similarly named gold products or currencies.
Market data · deployment planning
Gold WebSocket Feed
Stream the chosen gold instrument with a message contract that describes prices, session state and recovery.
Freshness on screen
A persistent socket should not keep a stale gold quote visually current. Monitor the observation age, expose unavailable or closed status and define the snapshot procedure used after reconnecting.
Requirements to confirm
- Instrument-specific channel
- Timestamp and status fields
- Stale display behavior
- Recovery snapshot checks
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 WebSocket Feed: what to agree before connecting
| Subscription scope | Specify symbol identifiers, supported fields and acknowledgement or rejection behaviour. |
|---|---|
| Quote semantics | Agree snapshot versus incremental updates, source timestamps and status fields. |
| Consumer pressure | Define application buffer limits and what happens when a consumer cannot process updates fast enough. |
| Reconnect rules | Agree authentication, resubscription, fresh snapshot and duplicate-message handling. |
Recover application state explicitly
For precious metals, define what a new subscriber receives before incremental updates begin. A connected socket does not prove a symbol is fresh. Separate heartbeat health from per-symbol timestamps and document the resubscription procedure after a disconnect.
What to test
- Disconnect during active updates and rebuild a current symbol state.
- Slow the consumer and observe the agreed buffering behaviour.
- Distinguish an inactive instrument from a stalled subscription.
{
"type": "quote",
"symbol": "XAUUSD",
"bid": "100.00",
"ask": "100.10",
"source_time": "2026-10-18T12:00:00.000Z",
"received_at": "2026-10-18T12:00:00.012Z",
"source_id": "example-source",
"status": "illustrative"
}Illustrative engineering example, not live prices or a published API contract. Confirm field names and delivery rules during integration.