Digital-asset identifiers
Resolve asset aliases and distinguish spot pairs from perpetual or dated derivatives. A symbol alone may be insufficient: include the venue and instrument type in the mapping approved for the session.
Use FIX for a crypto market-data workflow when the counterparties share a clear dictionary for venue, market type and quote fields.
Resolve asset aliases and distinguish spot pairs from perpetual or dated derivatives. A symbol alone may be insufficient: include the venue and instrument type in the mapping approved for the session.
Agree session resets and recovery around a continuously traded market. Operational runbooks should identify whether maintenance interrupts subscriptions, how clients reconnect and which observations are safe to use after restoration.
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 digital assets 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.