| ID | MsgType | Abbr | Flow |
|---|---|---|---|
| 13 | C |
| Added | EP | Updated | EP | Deprecated | EP |
|---|---|---|---|---|---|
| FIX.2.7 |
| ID | Name | Abbr | Presence | Description |
|---|---|---|---|---|
| 1024 | StandardHeader | BaseHeader | required | SYNOPSIS:
The standard FIX message header
ELABORATION: |
| 164 | EmailThreadID | EmailThreadID | required | SYNOPSIS:
Unique identifier for an email thread (new and chain of replies)
|
| 94 | EmailType | EmailTyp | required | SYNOPSIS:
Email message type.
|
| 42 | OrigTime | OrigTm | optional | SYNOPSIS:
Time of message origination (always expressed in UTC (Universal Time Coordinated, also known as "GMT"))
|
| 147 | Subject | Subject | required | SYNOPSIS:
The subject of an Email message
|
| 356 | EncodedSubjectLen | EncSubjectLen | optional | SYNOPSIS:
Byte length of encoded (non-ASCII characters) EncodedSubject (357) field.
|
| 357 | EncodedSubject | EncSubject | optional | SYNOPSIS:
Encoded (non-ASCII characters) representation of the Subject (147) field in the encoded format specified via the MessageEncoding (347) field. If used, the ASCII (English) representation should also be specified in the Subject field.
|
| 2054 | RoutingGrp | Rtg | optional | SYNOPSIS:
The RoutingGrp is used to allow the application message sender to instruct the intermediary distributing the message who to further send the application message to. The original sender may also instruct who is not allowed to receive the message. When provided, the routing instructions provided in this component are effective on a message by message basis.
ELABORATION: |
| 2017 | InstrmtGrp | Inst | optional | SYNOPSIS: ELABORATION: |
| 2066 | UndInstrmtGrp | Undly | optional | SYNOPSIS: ELABORATION: |
| 2019 | InstrmtLegGrp | Leg | optional | SYNOPSIS: ELABORATION: |
| 37 | OrderID | OrdID | optional | SYNOPSIS:
Unique identifier for Order as assigned by sell-side (broker, exchange, ECN). Uniqueness must be guaranteed within a single trading day. Firms which accept multi-day orders should consider embedding a date within the OrderID field to assure uniqueness across days.
|
| 11 | ClOrdID | ClOrdID | optional | SYNOPSIS:
Unique identifier for Order as assigned by the buy-side (institution, broker, intermediary etc.) (identified by SenderCompID (49) or OnBehalfOfCompID (5) as appropriate). Uniqueness must be guaranteed within a single trading day. Firms, particularly those which electronically submit multi-day orders, trade globally or throughout market close periods, should ensure uniqueness across days, for example by embedding a date within the ClOrdID field.
|
| 2029 | LinesOfTextGrp | TxtLn | required | SYNOPSIS: ELABORATION: |
| 95 | RawDataLength | RawDataLength | optional | SYNOPSIS:
Number of bytes in raw data field.
|
| 96 | RawData | RawData | optional | SYNOPSIS:
Unformatted raw data, can include bitmaps, word processor documents, etc.
|
| 2234 | AttachmentGrp | Attchmnt | optional | SYNOPSIS:
The AttachmentGrp component provides the ability to attach other media type documents to a FIX message for transmission. The media type can be any of the media types (previously referred to as MIME types) that are listed by IANA (www.iana.org) [RFC2046].
The AttachmentGrp is intended to be used to attach documents in other formats, such as PDF, TIFF, and Microsoft Word, for example to a FIX message.
Note when the AttachmentGrp is used within a business message, such as the TradeCaptureReport(35=AE), the attachment should supplement the data already contained in the business message It is not intended to replace the content of the business message. The standard fields within the business message should be populated, even if they duplicate data expressed within the attachment(s).
ELABORATION: |
| 1025 | StandardTrailer | Trlr | required | SYNOPSIS:
The standard FIX message trailer
ELABORATION: |