LegStipulationValue (FIX tag 689)

StringFIX 4.4

LegStipulationValue (tag 689) is a String field defined in FIX 4.4. It appears in 12 message types, always optionally.

At a glance

Tag
689
Name
LegStipulationValue
Datatype
String
Dialects
FIX 4.4
Messages
12

What the specification says

For Fixed Income, value of stipulation. See StipulationValue (234) for description and valid values

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

A real message using tag 689

ExecutionReport · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength205
35MsgType8Execution Report
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
37OrderIDORD-10042
17ExecIDEXEC-88117
150ExecType0New
39OrdStatus0New
54Side1Buy
151LeavesQty0
14CumQty1000000
6AvgPx1.09215
555NoLegs1 entry1repeating group
600LegSymbolEXAMPLE
683NoLegStipulations2 entries2repeating group
688LegStipulationTypeEXAMPLE
689LegStipulationValueEXAMPLE
688LegStipulationTypeEXAMPLE
689LegStipulationValueEXAMPLE
10CheckSum218
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 689 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.

MessageMsgTypeRequirednessWhere in the message
ExecutionReport8Optionalinside InstrmtLegExecGrp › LegStipulations
IOI6Optionalinside InstrmtLegIOIGrp › LegStipulations
MultilegOrderCancelReplaceACOptionalinside LegOrdGrp › LegStipulations
NewOrderMultilegABOptionalinside LegOrdGrp › LegStipulations
QuoteSOptionalinside LegQuotGrp › LegStipulations
QuoteRequestROptionalinside QuotReqGrp › QuotReqLegsGrp › LegStipulations
QuoteRequestRejectAGOptionalinside QuotReqRjctGrp › QuotReqLegsGrp › LegStipulations
QuoteResponseAJOptionalinside LegQuotGrp › LegStipulations
QuoteStatusReportAIOptionalinside LegQuotStatGrp › LegStipulations
SecurityListyOptionalinside SecListGrp › InstrmtLegSecListGrp › LegStipulations
TradeCaptureReportAEOptionalinside TrdInstrmtLegGrp › LegStipulations
TradeCaptureReportAckAROptionalinside TrdInstrmtLegGrp › LegStipulations

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 689 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[689];field?.name;   // "LegStipulationValue"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a string

Other String fields

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