Boar Team
GitHub

Text (FIX tag 58)

StringFIX 4.4FIX 4.2

Text (tag 58) is a String field defined in FIX 4.4 and FIX 4.2. It appears in 71 message types and is required in 2 of them.

At a glance

Tag
58
Name
Text
Datatype
String
Dialects
FIX 4.4 and FIX 4.2
Messages
71

What the specification says

Free format text string (Note: this field does not have a specified maximum length)

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

A real message using tag 58

NewOrderSingle · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength165
35MsgTypeDOrder – Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
58TextExample message generated from the FIX dictionary.
10CheckSum004
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 58 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.

MessageMsgTypeFIX 4.4FIX 4.2Where in the message
Advertisement7OptionalOptionaldirectly on the message body
AllocationInstructionJOptionalOptionaldirectly on the message body
AllocationInstructionAckPOptionalOptionaldirectly on the message body
AllocationReportASOptional—directly on the message body
AllocationReportAckATOptional—directly on the message body
AssignmentReportAWOptional—directly on the message body
BidRequestkOptionalOptionaldirectly on the message body
BidResponselOptionalOptionalinside the BidCompRspGrp component
BusinessMessageRejectjOptionalOptionaldirectly on the message body
CollateralAssignmentAYOptional—directly on the message body
CollateralInquiryBBOptional—directly on the message body
CollateralInquiryAckBGOptional—directly on the message body
CollateralReportBAOptional—directly on the message body
CollateralRequestAXOptional—directly on the message body
CollateralResponseAZOptional—directly on the message body
ConfirmationAKOptional—directly on the message body
ConfirmationAckAUOptional—directly on the message body
ConfirmationRequestBHOptional—directly on the message body
CrossOrderCancelReplaceRequesttOptional—inside the SideCrossOrdModGrp component
CrossOrderCancelRequestuOptional—inside the SideCrossOrdCxlGrp component
DerivativeSecurityListAAOptional—inside the RelSymDerivSecGrp component
DerivativeSecurityListRequestzOptional—directly on the message body
DontKnowTradeQOptionalOptionaldirectly on the message body
EmailCRequiredRequiredinside the LinesOfTextGrp component
ExecutionReport8OptionalOptionaldirectly on the message body
IOI6OptionalOptionaldirectly on the message body
ListCancelRequestKOptionalOptionaldirectly on the message body
ListExecuteLOptionalOptionaldirectly on the message body
ListStatusNOptionalOptionalinside the OrdListStatGrp component
ListStatusRequestMOptionalOptionaldirectly on the message body
ListStrikePricemOptionalOptionalinside the UndInstrmtStrkPxGrp component
Logout5OptionalOptionaldirectly on the message body
MarketDataIncrementalRefreshXOptionalOptionalinside the MDIncGrp component
MarketDataRequestRejectYOptionalOptionaldirectly on the message body
MarketDataSnapshotFullRefreshWOptionalOptionalinside the MDFullGrp component
MassQuoteAcknowledgementbOptionalOptionaldirectly on the message body
MultilegOrderCancelReplaceACOptional—directly on the message body
NewOrderCrosssOptional—inside the SideCrossOrdModGrp component
NewOrderListEOptionalOptionalinside the ListOrdGrp component
NewOrderMultilegABOptional—directly on the message body
NewOrderSingleDOptionalOptionaldirectly on the message body
NewsBRequiredRequiredinside the LinesOfTextGrp component
OrderCancelReject9OptionalOptionaldirectly on the message body
OrderCancelReplaceRequestGOptionalOptionaldirectly on the message body
OrderCancelRequestFOptionalOptionaldirectly on the message body
OrderMassCancelReportrOptional—directly on the message body
OrderMassCancelRequestqOptional—directly on the message body
PositionMaintenanceReportAMOptional—directly on the message body
PositionMaintenanceRequestALOptional—directly on the message body
PositionReportAPOptional—directly on the message body
QuoteSOptional—directly on the message body
QuoteRequestROptional—directly on the message body
QuoteRequestRejectAGOptional—directly on the message body
QuoteResponseAJOptional—directly on the message body
QuoteStatusReportAIOptional—directly on the message body
Reject3OptionalOptionaldirectly on the message body
RequestForPositionsANOptional—directly on the message body
RequestForPositionsAckAOOptional—directly on the message body
SecurityDefinitiondOptionalOptionaldirectly on the message body
SecurityDefinitionRequestcOptionalOptionaldirectly on the message body
SecurityListyOptional—inside the SecListGrp component
SecurityListRequestxOptional—directly on the message body
SecurityStatusfOptional—directly on the message body
SecurityTypeRequestvOptional—directly on the message body
SecurityTypeswOptional—directly on the message body
SettlementInstructionsTOptional—directly on the message body
TradeCaptureReportAEOptional—inside the TrdCapRptSideGrp component
TradeCaptureReportAckAROptional—directly on the message body
TradeCaptureReportRequestADOptional—directly on the message body
TradeCaptureReportRequestAckAQOptional—directly on the message body
TradingSessionStatushOptionalOptionaldirectly 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 58 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[58];field?.name;   // "Text"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
Try the decoderSource on GitHub