BenchmarkCurveName (FIX tag 221)

StringFIX 4.4

BenchmarkCurveName (tag 221) is a String field defined in FIX 4.4. It appears in 22 message types, always optionally.

At a glance

Tag
221
Name
BenchmarkCurveName
Datatype
String
Dialects
FIX 4.4
Messages
22

What the specification says

Name of benchmark curve.

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

A real message using tag 221

NewOrderSingle · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength123
35MsgTypeDOrder – Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
221BenchmarkCurveNameEXAMPLE
10CheckSum210
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 221 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
AllocationInstructionJOptionalinside the SpreadOrBenchmarkCurveData component
AllocationReportASOptionalinside the SpreadOrBenchmarkCurveData component
CollateralAssignmentAYOptionalinside the SpreadOrBenchmarkCurveData component
CollateralInquiryBBOptionalinside the SpreadOrBenchmarkCurveData component
CollateralReportBAOptionalinside the SpreadOrBenchmarkCurveData component
CollateralRequestAXOptionalinside the SpreadOrBenchmarkCurveData component
CollateralResponseAZOptionalinside the SpreadOrBenchmarkCurveData component
ConfirmationAKOptionalinside the SpreadOrBenchmarkCurveData component
CrossOrderCancelReplaceRequesttOptionalinside the SpreadOrBenchmarkCurveData component
ExecutionReport8Optionalinside the SpreadOrBenchmarkCurveData component
IOI6Optionalinside the SpreadOrBenchmarkCurveData component
NewOrderCrosssOptionalinside the SpreadOrBenchmarkCurveData component
NewOrderListEOptionalinside ListOrdGrp › SpreadOrBenchmarkCurveData
NewOrderSingleDOptionalinside the SpreadOrBenchmarkCurveData component
OrderCancelReplaceRequestGOptionalinside the SpreadOrBenchmarkCurveData component
QuoteSOptionalinside the SpreadOrBenchmarkCurveData component
QuoteRequestROptionalinside QuotReqGrp › SpreadOrBenchmarkCurveData
QuoteRequestRejectAGOptionalinside QuotReqRjctGrp › SpreadOrBenchmarkCurveData
QuoteResponseAJOptionalinside the SpreadOrBenchmarkCurveData component
QuoteStatusReportAIOptionalinside the SpreadOrBenchmarkCurveData component
SecurityListyOptionalinside SecListGrp › SpreadOrBenchmarkCurveData
TradeCaptureReportAEOptionalinside the SpreadOrBenchmarkCurveData component

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 221 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[221];field?.name;   // "BenchmarkCurveName"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