LegBenchmarkPrice (FIX tag 679)

PriceFIX 4.4

LegBenchmarkPrice (tag 679) is a Price field defined in FIX 4.4. It appears in 5 message types, always optionally.

At a glance

Tag: 679
Name: LegBenchmarkPrice
Datatype: Price (float)
Dialects: FIX 4.4
Messages: 5

What the specification says

Used to identify the price of the benchmark security. See BenchmarkPrice (662) for description and valid values.

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

A real message using tag 679

Quote · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	129
35	MsgType	S	Quote
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
117	QuoteID	EXAMPLE
555	NoLegs2 entries	2	repeating group
600	LegSymbol	EXAMPLE
679	LegBenchmarkPrice	1.09210
600	LegSymbol	EXAMPLE
679	LegBenchmarkPrice	1.09210
10	CheckSum	052

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 679 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
Quote	S	Optional	inside LegQuotGrp › LegBenchmarkCurveData
QuoteRequest	R	Optional	inside QuotReqGrp › QuotReqLegsGrp › LegBenchmarkCurveData
QuoteRequestReject	AG	Optional	inside QuotReqRjctGrp › QuotReqLegsGrp › LegBenchmarkCurveData
QuoteResponse	AJ	Optional	inside LegQuotGrp › LegBenchmarkCurveData
SecurityList	y	Optional	inside SecListGrp › InstrmtLegSecListGrp › LegBenchmarkCurveData

Wire format

A decimal price. Precision is a venue convention, not a protocol rule, so compare the raw string when exactness matters. @boarteam/fix parses the value as a number and reports parse/invalid-float when it does not lex as one; the raw string is kept so precision and trailing zeros are never lost.

Read tag 679 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[679];field?.name;   // "LegBenchmarkPrice"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a number

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