OrderID (FIX tag 37)

StringFIX 4.4FIX 4.2FIX 5.0 SP2

OrderID (tag 37) is a String field defined in FIX 4.4, FIX 4.2 and FIX 5.0 SP2. It appears in 25 message types and is required in 5 of them.

At a glance

Tag: 37
Name: OrderID
Datatype: String
Dialects: FIX 4.4, FIX 4.2 and FIX 5.0 SP2
Messages: 25

What the specification says

FIX 4.4

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.

FIX 4.2

Unique identifier for Order as assigned by broker. 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.

FIX 5.0 SP2

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.

Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.

A real message using tag 37

MarketDataSnapshotFullRefresh · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	107
35	MsgType	W	Market Data-Snapshot/Full Refresh
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
268	NoMDEntries2 entries	2	repeating group
269	MDEntryType	0	Bid
37	OrderID	ORD-10042
269	MDEntryType	0	Bid
37	OrderID	ORD-10042
10	CheckSum	148

Edit and decode it yourself

Shown with | separators for readability. On the wire FIX uses SOH (0x01), an invisible control byte — and because BodyLength and CheckSum are computed over the actual bytes, the two forms have different checksums. Both are valid and both decode here.

Open in the full decoder →

Generated from the FIX 4.4 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.

Where tag 37 appears

Requiredness is a property of the message, not of the field: the same tag can be optional in one message and conditionally required in another.

Message	MsgType	FIX 4.4	FIX 4.2	FIX 5.0 SP2	Where in the message
AllocationInstruction	J	Optional	Optional	Optional	inside the OrdAllocGrp component
AllocationInstructionAlert	BM	—	—	Optional	inside the OrdAllocGrp component
AllocationReport	AS	Optional	—	Optional	inside the OrdAllocGrp component
CollateralAssignment	AY	Optional	—	Optional	directly on the message body
CollateralInquiry	BB	Optional	—	Optional	directly on the message body
CollateralInquiryAck	BG	Optional	—	Optional	directly on the message body
CollateralReport	BA	Optional	—	Optional	directly on the message body
CollateralRequest	AX	Optional	—	Optional	directly on the message body
CollateralResponse	AZ	Optional	—	Optional	directly on the message body
Confirmation	AK	Optional	—	Optional	inside the OrdAllocGrp component
ConfirmationRequest	BH	Optional	—	Optional	inside the OrdAllocGrp component
CrossOrderCancelReplaceRequest	t	Optional	—	Optional	directly on the message body
CrossOrderCancelRequest	u	Optional	—	Optional	directly on the message body
DontKnowTrade	Q	Required	Required	Required	directly on the message body
Email	C	Optional	Optional	Optional	directly on the message body
ExecutionAcknowledgement	BN	—	—	Required	directly on the message body
ExecutionReport	8	Required	Required	Required	directly on the message body
ListStatus	N	—	—	Optional	inside the OrdListStatGrp component
MarketDataIncrementalRefresh	X	Optional	Optional	Optional	inside the MDIncGrp component
MarketDataSnapshotFullRefresh	W	Optional	Optional	Optional	inside the MDFullGrp component
MultilegOrderCancelReplace	AC	Optional	—	Optional	directly on the message body
OrderCancelReject	9	Required	Required	Required	directly on the message body
OrderCancelReplaceRequest	G	Optional	Optional	Optional	directly on the message body
OrderCancelRequest	F	Optional	Optional	Optional	directly on the message body
OrderMassCancelReport	r	Required	—	Required	directly on the message body
OrderStatusRequest	H	Optional	Optional	Optional	directly on the message body
TradeCaptureReport	AE	Required	—	Optional	inside the TrdCapRptSideGrp component
TradeCaptureReportAck	AR	—	—	Optional	inside TrdCapRptAckSideGrp › TradeReportOrderDetail
TradeCaptureReportRequest	AD	Optional	—	Optional	directly on the message body

Wire format

Free-form text. Any byte except the SOH separator is legal, so values are not trimmed or case-folded on the wire. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.

Read tag 37 in TypeScript

decode.tsts

import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix44";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const field = message.fields[37];field?.name;   // "OrderID"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a string

Decode this in your own code

The same engine that produced the decoded example above is an Apache-2.0 npm package with zero runtime dependencies. It runs in Node and in the browser, and parse() returns problems as data instead of throwing.

npm i @boarteam/fix @boarteam/fix-dict-fix44

Try the decoder Source on GitHub