Tag number, field name, MsgType, message or component name, or a value such as 39=1 or OrdStatus=2. Search runs in your browser.
OrderID <37>
- Tag
37- Type
- String
- FIXML name
OrdID- Pedigree
- Added FIX 2.7
- Versions
- FIX Latest ✓ · FIX 4.4 ✓ · FIX 4.2 ✓
This page shows OrderID <37> as defined in FIX 4.4. For the current standard, see tag 37 OrderID in FIX Latest.
OrderID <37> in plain English
Summary by The MidPoint News, based on the description in the Orchestra file (quoted in full below).
OrderID is the sell side's unique identifier for an order, assigned by the broker, exchange or ECN. It must be unique within a trading day, and the Orchestra file suggests embedding a date for multi-day orders.
Where it is used
ExecutionReport (35=8), OrderCancelRequest (35=F), OrderCancelReplaceRequest (35=G), OrderCancelReject (35=9), Email (35=C), OrderStatusRequest (35=H), DontKnowTrade (35=Q), OrderMassCancelReport (35=r) and 14 more.
In all, 25 messages in FIX 4.4 can carry it. Full list.
Example message
8=FIX.4.4|9=210|35=8|49=BUYSIDE|56=SELLSIDE|34=215|52=20261116-08:30:00.000|37=OID-5001|11=ORD-1001|17=EXEC-7001|150=F|39=1|55=AAPL|54=1|38=1000|40=2|44=190.50|32=400|31=190.48|151=600|14=400|6=190.48|60=20261116-08:30:00.000|10=045 Illustrative example, not real orders or market data. An ExecutionReport (35=8) in FIX 4.4, shown with BeginString FIX.4.4. Instrument identifiers (such as AAPL, ISIN US0378331005, ESZ6, XNAS, XCME) are real public codes used for illustration. Order and execution IDs, accounts, prices, quantities and times are made up. Fields are separated by | here; on the wire the separator is the SOH character (ASCII 1). BodyLength (9) and CheckSum (10) are calculated for this example. Every tag and value in it is checked against the FIX 4.4 dictionary, but it is not a complete specification of the message.
Description (from the Orchestra file)
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.
Used in
Messages (18)
| Message | MsgType | Presence |
|---|---|---|
| ExecutionReport | 8 | Required |
| OrderCancelReject | 9 | Required |
| C | Optional | |
| OrderCancelRequest | F | Optional |
| OrderCancelReplaceRequest | G | Optional |
| OrderStatusRequest | H | Optional |
| DontKnowTrade | Q | Required |
| OrderMassCancelReport | r | Required |
| CrossOrderCancelReplaceRequest | t | Optional |
| CrossOrderCancelRequest | u | Optional |
| MultilegOrderCancelReplace | AC | Optional |
| TradeCaptureReportRequest | AD | Optional |
| CollateralRequest | AX | Optional |
| CollateralAssignment | AY | Optional |
| CollateralResponse | AZ | Optional |
| CollateralReport | BA | Optional |
| CollateralInquiry | BB | Optional |
| CollateralInquiryAck | BG | Optional |
Components and repeating groups (4)
| Name | Kind | Presence |
|---|---|---|
| MDFullGrp | Repeating group | Optional |
| MDIncGrp | Repeating group | Optional |
| OrdAllocGrp | Repeating group | Optional |
| TrdCapRptSideGrp | Repeating group | Required |
All 25 messages that can carry OrderID, including through components and groups
- AllocationInstruction
- AllocationReport
- CollateralAssignment
- CollateralInquiry
- CollateralInquiryAck
- CollateralReport
- CollateralRequest
- CollateralResponse
- Confirmation
- ConfirmationRequest
- CrossOrderCancelReplaceRequest
- CrossOrderCancelRequest
- DontKnowTrade
- ExecutionReport
- MarketDataIncrementalRefresh
- MarketDataSnapshotFullRefresh
- MultilegOrderCancelReplace
- OrderCancelReject
- OrderCancelReplaceRequest
- OrderCancelRequest
- OrderMassCancelReport
- OrderStatusRequest
- TradeCaptureReport
- TradeCaptureReportRequest