ConfirmReqID (FIX tag 859)

StringFIX 4.4

ConfirmReqID (tag 859) is a String field defined in FIX 4.4. It appears in 2 message types and is required in 1 of them.

At a glance

Tag: 859
Name: ConfirmReqID
Datatype: String
Dialects: FIX 4.4
Messages: 2

What the specification says

Unique identifier for a Confirmation Request message

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

A real message using tag 859

Confirmation · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	232
35	MsgType	AK	Confirmation
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
664	ConfirmID	EXAMPLE
859	ConfirmReqID	EXAMPLE
666	ConfirmTransType	0	New
773	ConfirmType	1	Status
665	ConfirmStatus	1	Received
60	TransactTime	20240101-12:00:00.000
75	TradeDate	20240101
80	AllocQty	1000000
54	Side	1	Buy
862	NoCapacities1 entry	1	repeating group
528	OrderCapacity	A	Agency
863	OrderCapacityQty	1000000
79	AllocAccount	EXAMPLE
6	AvgPx	1.09215
381	GrossTradeAmt	125000.00
118	NetMoney	125000.00
10	CheckSum	254

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 859 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
Confirmation	AK	Optional	directly on the message body
ConfirmationRequest	BH	Required	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 859 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[859];field?.name;   // "ConfirmReqID"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