FIX Protocol Tag 100: ExDestination

Practical notes on ExDestination

ExDestination names where the order should be executed, such as a specific exchange.

• From FIX 4.2 it usually carries a market identifier code (MIC, ISO 10383), but brokers often define their own destination codes.
• It is a routing instruction. SecurityExchange (207) describes the instrument's market, which is a different thing.

Common mistakes

• Using the broker's code list on one session and MICs on another without mapping.

Tag 100 in each FIX version

Values and message usage as defined in a specific version.

• FIX 4.0
• FIX 4.1
• FIX 4.2
• FIX 4.3
• FIX 4.4
• FIX 5.0
• FIX 5.0 SP1
• FIX 5.0 SP2

Data type

EXCHANGE: A market or exchange, usually given as an ISO 10383 market identifier code (MIC), such as XNYS.

Valid values

2 enumerated values across all FIX versions.

Example

100=0

Illustrative value. In a message, fields are separated by the SOH character (0x01), often shown as | or ^ in logs.

Message types that use tag 100

• Execution Report 35=8
• Order Cancel Reject 35=9
• New Order Single 35=D
• New Order List 35=E
• Order Cancel Request 35=F
• Order Cancel/Replace Request 35=G
• Quote 35=S
• New Order Multileg 35=AB
• Multileg Order Cancel/Replace 35=AC
• Quote Status Report 35=AI
• Quote Response 35=AJ
• New Order Cross 35=s
• Cross Order Cancel Replace Request 35=t

Covers every version from FIX 4.0 to 5.0 SP2, including fields reached through components and repeating groups. The version pages above show whether the tag is required in each message.