ListRejectReason (FIX tag 1386)

intFIX 5.0 SP2

ListRejectReason (tag 1386) is an int field defined in FIX 5.0 SP2. It appears in 1 message type, always optionally. It is an enumerated field with 7 defined values.

At a glance

Tag: 1386
Name: ListRejectReason
Datatype: int
Dialects: FIX 5.0 SP2
Messages: 1
Valid values: 7

What the specification says

Identifies the reason for rejection of a New Order List message. Note that OrdRejReason(103) is used if the rejection is based on properties of an individual order part of the List.

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

A real message using tag 1386

ListStatus · FIX 5.0 SP2

Tag	Field	Wire value	Meaning
8	BeginString	FIXT.1.1
9	BodyLength	169
35	MsgType	N	ListStatus
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
66	ListID	EXAMPLE
429	ListStatusType	1	Ack
82	NoRpts	1
431	ListOrderStatus	1	In bidding process
1386	ListRejectReason	0	Broker / Exchange option
83	RptSeq	1
68	TotNoOrders	1
73	NoOrders1 entry	1	repeating group
11	ClOrdID	ORD-10042
14	CumQty	1000000
39	OrdStatus	0	New
151	LeavesQty	0
84	CxlQty	1000000
6	AvgPx	1.09215
10	CheckSum	016

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 5.0 SP2 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.

Valid values

A value outside this list is not a parse error — the message still decodes — but validate() reports it as validate/value-not-in-enum.

Value	Meaning	Symbolic name
0	Broker / Exchange option	BROKER_EXCHANGE_OPTION
2	Exchange closed	EXCHANGE_CLOSED
4	Too late to enter	TOO_LATE_TO_ENTER
5	Unknown order	UNKNOWN_ORDER
6	Duplicate Order (e.g. dupe ClOrdID)	DUPLICATE_ORDER
11	Unsupported order characteristic	UNSUPPORTED_ORDER_CHARACTERISTIC
99	Other	OTHER

Where tag 1386 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	Requiredness	Where in the message
ListStatus	N	Optional	directly on the message body

Wire format

A whole number, optionally signed. Leading zeros are legal on the wire and are preserved in the raw value. @boarteam/fix parses the value as a number and reports parse/invalid-int when it does not lex as one; the raw string is kept either way.

Read tag 1386 in TypeScript

decode.tsts

import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix50sp2";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const listRejectReason = message.fields[1386]?.raw;// e.g. "0" — Broker / Exchange option// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(1386)  ?.enumValues?.find((e) => e.value === listRejectReason)  ?.description;

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-fix50sp2

Try the decoder Source on GitHub