FIX Protocol Tag 126: ExpireTime
Date and time the order expires, in UTC, for orders that are good till a specific time.
- Tag number
- 126
- Data type
- UTCTIMESTAMP
- FIX versions
- FIX 4.0 to 5.0 SP2
- Used in
- 22 message types
Tag 126 in each FIX version
Values and message usage as defined in a specific version.
Data type
UTCTIMESTAMP: Date and time in UTC as YYYYMMDD-HH:MM:SS, optionally followed by fractions of a second (.sss).
Example
126=20261020-14:30:05.123
Illustrative value. In a message, fields are separated by the SOH character (0x01), often shown as | or ^ in logs.
Decode a message with this tagMessage types that use tag 126
- Execution Report 35=8
- New Order Single 35=D
- New Order List 35=E
- Order Cancel/Replace Request 35=G
- Quote Request 35=R
- Settlement Instructions 35=T
- Market Data Snapshot Full Refresh 35=W
- Market Data Incremental Refresh 35=X
- New Order Multileg 35=AB
- Multileg Order Cancel/Replace 35=AC
- Trade Capture Report 35=AE
- Quote Request Reject 35=AG
- Quote Status Report 35=AI
- Trade Capture Report Ack 35=AR
- Settlement Instruction Request 35=AV
- Collateral Request 35=AX
- Collateral Assignment 35=AY
- Settlement Obligation Report 35=BQ
- Trade Match Report 35=DC
- Party Risk Limit Check Request Ack 35=DG
- 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.
Field and message data comes from the QuickFIX data dictionaries for FIX 4.0 to 5.0 SP2 and FIXT 1.1, used under the QuickFIX Software License. This product includes software developed by quickfixengine.org (http://www.quickfixengine.org/). Enumerated value names are converted to plain text for reading.