ClientBidID (FIX tag 391)

StringFIX 4.4FIX 4.2

ClientBidID (tag 391) is a String field defined in FIX 4.4 and FIX 4.2. It appears in 4 message types and is required in 1 of them.

At a glance

Tag: 391
Name: ClientBidID
Datatype: String
Dialects: FIX 4.4 and FIX 4.2
Messages: 4

What the specification says

Unique identifier for a Bid Request as assigned by institution. Uniqueness must be guaranteed within a single trading day.

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

A real message using tag 391

NewOrderList · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	125
35	MsgType	E	Order – List
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
66	ListID	EXAMPLE
391	ClientBidID	EXAMPLE
394	BidType	1	"Non Disclosed" Style (e.g. US/European)
68	TotNoOrders	1
73	NoOrders1 entry	1	repeating group
11	ClOrdID	ORD-10042
67	ListSeqNo	1
54	Side	1	Buy
10	CheckSum	177

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 391 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	Where in the message
BidRequest	k	Required	Required	directly on the message body
BidResponse	l	Optional	Optional	directly on the message body
ListExecute	L	Optional	Optional	directly on the message body
NewOrderList	E	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 391 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[391];field?.name;   // "ClientBidID"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