Text (FIX tag 58)

StringFIX 4.4FIX 4.2FIX 5.0 SP2

Text (tag 58) is a String field defined in FIX 4.4, FIX 4.2 and FIX 5.0 SP2. 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, FIX 4.2 and FIX 5.0 SP2
Messages
71

What the specification says

FIX 4.4

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

FIX 4.2

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

FIX 5.0 SP2

Free format text string often populated with error messages or warnings.

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.2FIX 5.0 SP2Where in the message
Advertisement7OptionalOptionalOptionaldirectly on the message body
AllocationInstructionJOptionalOptionalOptionaldirectly on the message body
AllocationInstructionAckPOptionalOptionalOptionaldirectly on the message body
AllocationInstructionAlertBM——Optionaldirectly on the message body
AllocationReportASOptional—Optionaldirectly on the message body
AllocationReportAckATOptional—Optionaldirectly on the message body
ApplicationMessageReportBY——Optionaldirectly on the message body
ApplicationMessageRequestBW——Optionaldirectly on the message body
ApplicationMessageRequestAckBX——Optionaldirectly on the message body
AssignmentReportAWOptional—Optionaldirectly on the message body
BidRequestkOptionalOptionalOptionaldirectly on the message body
BidResponselOptionalOptionalOptionalinside the BidCompRspGrp component
BusinessMessageRejectjOptionalOptionalOptionaldirectly on the message body
CollateralAssignmentAYOptional—Optionaldirectly on the message body
CollateralInquiryBBOptional—Optionaldirectly on the message body
CollateralInquiryAckBGOptional—Optionaldirectly on the message body
CollateralReportBAOptional—Optionaldirectly on the message body
CollateralRequestAXOptional—Optionaldirectly on the message body
CollateralResponseAZOptional—Optionaldirectly on the message body
ConfirmationAKOptional—Optionaldirectly on the message body
ConfirmationAckAUOptional—Optionaldirectly on the message body
ConfirmationRequestBHOptional—Optionaldirectly on the message body
ContraryIntentionReportBO——Optionaldirectly on the message body
CrossOrderCancelReplaceRequesttOptional—Optionalinside the SideCrossOrdModGrp component
CrossOrderCancelRequestuOptional—Optionalinside the SideCrossOrdCxlGrp component
DerivativeSecurityListAAOptional—Optionalinside the RelSymDerivSecGrp component
DerivativeSecurityListRequestzOptional—Optionaldirectly on the message body
DerivativeSecurityListUpdateReportBR——Optionalinside the RelSymDerivSecUpdGrp component
DontKnowTradeQOptionalOptionalOptionaldirectly on the message body
EmailCRequiredRequiredRequiredinside the LinesOfTextGrp component
ExecutionAcknowledgementBN——Optionaldirectly on the message body
ExecutionReport8OptionalOptionalOptionaldirectly on the message body
IOI6OptionalOptionalOptionaldirectly on the message body
ListCancelRequestKOptionalOptionalOptionaldirectly on the message body
ListExecuteLOptionalOptionalOptionaldirectly on the message body
ListStatusNOptionalOptionalOptionalinside the OrdListStatGrp component
ListStatusRequestMOptionalOptionalOptionaldirectly on the message body
ListStrikePricemOptionalOptionalOptionalinside the UndInstrmtStrkPxGrp component
LogonA——Optionaldirectly on the message body
Logout5OptionalOptionalOptionaldirectly on the message body
MarketDataIncrementalRefreshXOptionalOptionalOptionalinside the MDIncGrp component
MarketDataRequestRejectYOptionalOptionalOptionaldirectly on the message body
MarketDataSnapshotFullRefreshWOptionalOptionalOptionalinside the MDFullGrp component
MarketDefinitionBU——Optionaldirectly on the message body
MarketDefinitionUpdateReportBV——Optionaldirectly on the message body
MassQuoteAcknowledgementbOptionalOptionalOptionaldirectly on the message body
MultilegOrderCancelReplaceACOptional—Optionaldirectly on the message body
NewOrderCrosssOptional—Optionalinside the SideCrossOrdModGrp component
NewOrderListEOptionalOptionalOptionalinside the ListOrdGrp component
NewOrderMultilegABOptional—Optionaldirectly on the message body
NewOrderSingleDOptionalOptionalOptionaldirectly on the message body
NewsBRequiredRequiredRequiredinside the LinesOfTextGrp component
OrderCancelReject9OptionalOptionalOptionaldirectly on the message body
OrderCancelReplaceRequestGOptionalOptionalOptionaldirectly on the message body
OrderCancelRequestFOptionalOptionalOptionaldirectly on the message body
OrderMassActionReportBZ——Optionaldirectly on the message body
OrderMassActionRequestCA——Optionaldirectly on the message body
OrderMassCancelReportrOptional—Optionaldirectly on the message body
OrderMassCancelRequestqOptional—Optionaldirectly on the message body
PositionMaintenanceReportAMOptional—Optionaldirectly on the message body
PositionMaintenanceRequestALOptional—Optionaldirectly on the message body
PositionReportAPOptional—Optionaldirectly on the message body
QuoteSOptional—Optionaldirectly on the message body
QuoteRequestROptional—Optionaldirectly on the message body
QuoteRequestRejectAGOptional—Optionaldirectly on the message body
QuoteResponseAJOptional—Optionaldirectly on the message body
QuoteStatusReportAIOptional—Optionaldirectly on the message body
Reject3OptionalOptionalOptionaldirectly on the message body
RequestForPositionsANOptional—Optionaldirectly on the message body
RequestForPositionsAckAOOptional—Optionaldirectly on the message body
SecurityDefinitiondOptionalOptionalOptionaldirectly on the message body
SecurityDefinitionRequestcOptionalOptionalOptionaldirectly on the message body
SecurityDefinitionUpdateReportBP——Optionaldirectly on the message body
SecurityListyOptional—Optionalinside the SecListGrp component
SecurityListRequestxOptional—Optionaldirectly on the message body
SecurityListUpdateReportBK——Optionalinside the SecLstUpdRelSymGrp component
SecurityStatusfOptional—Optionaldirectly on the message body
SecurityTypeRequestvOptional—Optionaldirectly on the message body
SecurityTypeswOptional—Optionaldirectly on the message body
SettlementInstructionsTOptional—Optionaldirectly on the message body
SettlementObligationReportBQ——Optionaldirectly on the message body
StreamAssignmentReportCD——Optionalinside StrmAsgnRptGrp › StrmAsgnRptInstrmtGrp
StreamAssignmentReportACKCE——Optionaldirectly on the message body
TradeCaptureReportAEOptional—Optionalinside the TrdCapRptSideGrp component
TradeCaptureReportAckAROptional—Optionaldirectly on the message body
TradeCaptureReportRequestADOptional—Optionaldirectly on the message body
TradeCaptureReportRequestAckAQOptional—Optionaldirectly on the message body
TradingSessionListBJ——Optionalinside the TrdSessLstGrp component
TradingSessionListUpdateReportBS——Optionalinside the TrdSessLstGrp component
TradingSessionStatushOptionalOptionalOptionaldirectly on the message body
UserNotificationCB——Optionaldirectly 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