Boar Team
GitHub

NewOrderList (MsgType E)

applicationFIX 4.4FIX 4.2

NewOrderList is the FIX message with MsgType E, defined in FIX 4.4 and FIX 4.2. It is an application-level message: it carries a business event rather than managing the session. Its body has 21 top-level members once the standard header and trailer are counted. Earlier dialects call it OrderList; the MsgType value is unchanged.

MsgType is case-sensitive
E is NewOrderList, but e is a different message entirely — SecurityStatusRequest. Twenty-three FIX message types differ from another only by letter case.
Also known as OrderList
FIX 4.2 calls MsgType E OrderList. Same value on the wire, different name in the spec.

A real NewOrderList

NewOrderList · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength113
35MsgTypeEOrder – List
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
66ListIDEXAMPLE
394BidType1"Non Disclosed" Style (e.g. US/European)
68TotNoOrders1
73NoOrders1 entry1repeating group
11ClOrdIDORD-10042
67ListSeqNo1
54Side1Buy
10CheckSum199
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.

Message body — FIX 4.4

Components are listed by name and link to their own page rather than being expanded inline; repeating groups are expanded, including where they nest.

Message body — FIX 4.2

Components are listed by name and link to their own page rather than being expanded inline; repeating groups are expanded, including where they nest.

What changed between the dialects

Present in FIX 4.4 only (8)

tag 480, tag 481, tag 513, tag 765, tag 766, tag 767, tag 893, ListOrdGrp

Present in FIX 4.2 only (1)

group 73

Handle NewOrderList 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);​if (message.msgType === "E") {  message.name;            // "NewOrderList"  // fields are keyed by tag; repeating groups live on message.groups}​// Problems come back as data, never as exceptions:issues;                    // FixIssue[]fix.validate(message);     // dictionary-level problems

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 decoderSource on GitHub