Drop Copy messages on the zerohash CLOB.
Welcome to the section dedicated to zerohash FIX Drop Copy Messages. Here, you will find detailed information about various FIX messages used for drop copy functionality in the zerohash trading system.Drop copy messages provide clients with copies of execution reports and other important trading information, facilitating transparency and risk management.
Explore the tables below to learn more about each drop copy message, their tags, field names, requirements, and additional notes.
Some additional notes:
- Multiple drop-copy sessions receive identical copies: If a firm has more than one drop-copy session configured (e.g. -DC-1, -DC-2, -DC-3), every ExecutionReport is delivered to each one independently. Sequence numbers are per-session, so the seqnum on the same execution will differ across sessions.
- Fanout is firm-level, not per order-entry session: Drop-copy sessions are not paired 1:1 with order-entry sessions. They subscribe to the entire firm's execution stream.
- Identifying the originating order-entry session: Use ClOrdID (tag 11) — the same ClOrdID the client set on submission is echoed back on the drop-copy. There is no ZH-added tag pointing to the OE session.
- Deduplication is the receiver's responsibility: ExecID (tag 17) is unique per execution and stable across all copies — dedupe on that if needed.
- Covers all trading activity for the firm: Includes orders submitted via any order-entry FIX session and via the zerohash REST API.
- All ExecType/OrdStatus values flow through: No filter by type (fills, cancels, replaces, rejects, pending states, trade corrections/cancels, etc)