BenchmarkCurveName (FIX tag 221)
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
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIX.4.4 | |
| 9 | BodyLength | 123 | |
| 35 | MsgType | D | Order – Single |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 11 | ClOrdID | ORD-10042 | |
| 54 | Side | 1 | Buy |
| 60 | TransactTime | 20240101-12:00:00.000 | |
| 40 | OrdType | 1 | Market |
| 221 | BenchmarkCurveName | EXAMPLE | |
| 10 | CheckSum | 210 |
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.
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.
| Message | MsgType | Requiredness | Where in the message |
|---|---|---|---|
| AllocationInstruction | J | Optional | inside the SpreadOrBenchmarkCurveData component |
| AllocationReport | AS | Optional | inside the SpreadOrBenchmarkCurveData component |
| CollateralAssignment | AY | Optional | inside the SpreadOrBenchmarkCurveData component |
| CollateralInquiry | BB | Optional | inside the SpreadOrBenchmarkCurveData component |
| CollateralReport | BA | Optional | inside the SpreadOrBenchmarkCurveData component |
| CollateralRequest | AX | Optional | inside the SpreadOrBenchmarkCurveData component |
| CollateralResponse | AZ | Optional | inside the SpreadOrBenchmarkCurveData component |
| Confirmation | AK | Optional | inside the SpreadOrBenchmarkCurveData component |
| CrossOrderCancelReplaceRequest | t | Optional | inside the SpreadOrBenchmarkCurveData component |
| ExecutionReport | 8 | Optional | inside the SpreadOrBenchmarkCurveData component |
| IOI | 6 | Optional | inside the SpreadOrBenchmarkCurveData component |
| NewOrderCross | s | Optional | inside the SpreadOrBenchmarkCurveData component |
| NewOrderList | E | Optional | inside ListOrdGrp › SpreadOrBenchmarkCurveData |
| NewOrderSingle | D | Optional | inside the SpreadOrBenchmarkCurveData component |
| OrderCancelReplaceRequest | G | Optional | inside the SpreadOrBenchmarkCurveData component |
| Quote | S | Optional | inside the SpreadOrBenchmarkCurveData component |
| QuoteRequest | R | Optional | inside QuotReqGrp › SpreadOrBenchmarkCurveData |
| QuoteRequestReject | AG | Optional | inside QuotReqRjctGrp › SpreadOrBenchmarkCurveData |
| QuoteResponse | AJ | Optional | inside the SpreadOrBenchmarkCurveData component |
| QuoteStatusReport | AI | Optional | inside the SpreadOrBenchmarkCurveData component |
| SecurityList | y | Optional | inside SecListGrp › SpreadOrBenchmarkCurveData |
| TradeCaptureReport | AE | Optional | inside 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
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 stringOther String fields
- 222BenchmarkCurvePoint
- 217RoutingID
- 214SettlInstRefID
- 233StipulationType
- 234StipulationValue
- 235YieldType
- 239RepoCollateralSecurityType
- 243UnderlyingRepoCollateralSecurityType
- 198SecondaryOrderID
- 196AllocLinkID
- 250LegRepoCollateralSecurityType
- 187CashSettlAgentContactPhone
- 255CreditRating
- 186CashSettlAgentContactName
- 256UnderlyingCreditRating
- 185CashSettlAgentAcctName
- 257LegCreditRating
- 184CashSettlAgentAcctNum
- 183CashSettlAgentCode
- 182CashSettlAgentName
- 181SecuritySettlAgentContactPhone
- 180SecuritySettlAgentContactName
- 262MDReqID
- 179SecuritySettlAgentAcctName
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