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
AllocationInstructionAlertBMOptionaldirectly on the message body
AllocationReportASOptionalOptionaldirectly on the message body
AllocationReportAckATOptionalOptionaldirectly on the message body
ApplicationMessageReportBYOptionaldirectly on the message body
ApplicationMessageRequestBWOptionaldirectly on the message body
ApplicationMessageRequestAckBXOptionaldirectly on the message body
AssignmentReportAWOptionalOptionaldirectly on the message body
BidRequestkOptionalOptionalOptionaldirectly on the message body
BidResponselOptionalOptionalOptionalinside the BidCompRspGrp component
BusinessMessageRejectjOptionalOptionalOptionaldirectly on the message body
CollateralAssignmentAYOptionalOptionaldirectly on the message body
CollateralInquiryBBOptionalOptionaldirectly on the message body
CollateralInquiryAckBGOptionalOptionaldirectly on the message body
CollateralReportBAOptionalOptionaldirectly on the message body
CollateralRequestAXOptionalOptionaldirectly on the message body
CollateralResponseAZOptionalOptionaldirectly on the message body
ConfirmationAKOptionalOptionaldirectly on the message body
ConfirmationAckAUOptionalOptionaldirectly on the message body
ConfirmationRequestBHOptionalOptionaldirectly on the message body
ContraryIntentionReportBOOptionaldirectly on the message body
CrossOrderCancelReplaceRequesttOptionalOptionalinside the SideCrossOrdModGrp component
CrossOrderCancelRequestuOptionalOptionalinside the SideCrossOrdCxlGrp component
DerivativeSecurityListAAOptionalOptionalinside the RelSymDerivSecGrp component
DerivativeSecurityListRequestzOptionalOptionaldirectly on the message body
DerivativeSecurityListUpdateReportBROptionalinside the RelSymDerivSecUpdGrp component
DontKnowTradeQOptionalOptionalOptionaldirectly on the message body
EmailCRequiredRequiredRequiredinside the LinesOfTextGrp component
ExecutionAcknowledgementBNOptionaldirectly 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
LogonAOptionaldirectly on the message body
Logout5OptionalOptionalOptionaldirectly on the message body
MarketDataIncrementalRefreshXOptionalOptionalOptionalinside the MDIncGrp component
MarketDataRequestRejectYOptionalOptionalOptionaldirectly on the message body
MarketDataSnapshotFullRefreshWOptionalOptionalOptionalinside the MDFullGrp component
MarketDefinitionBUOptionaldirectly on the message body
MarketDefinitionUpdateReportBVOptionaldirectly on the message body
MassQuoteAcknowledgementbOptionalOptionalOptionaldirectly on the message body
MultilegOrderCancelReplaceACOptionalOptionaldirectly on the message body
NewOrderCrosssOptionalOptionalinside the SideCrossOrdModGrp component
NewOrderListEOptionalOptionalOptionalinside the ListOrdGrp component
NewOrderMultilegABOptionalOptionaldirectly 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
OrderMassActionReportBZOptionaldirectly on the message body
OrderMassActionRequestCAOptionaldirectly on the message body
OrderMassCancelReportrOptionalOptionaldirectly on the message body
OrderMassCancelRequestqOptionalOptionaldirectly on the message body
PositionMaintenanceReportAMOptionalOptionaldirectly on the message body
PositionMaintenanceRequestALOptionalOptionaldirectly on the message body
PositionReportAPOptionalOptionaldirectly on the message body
QuoteSOptionalOptionaldirectly on the message body
QuoteRequestROptionalOptionaldirectly on the message body
QuoteRequestRejectAGOptionalOptionaldirectly on the message body
QuoteResponseAJOptionalOptionaldirectly on the message body
QuoteStatusReportAIOptionalOptionaldirectly on the message body
Reject3OptionalOptionalOptionaldirectly on the message body
RequestForPositionsANOptionalOptionaldirectly on the message body
RequestForPositionsAckAOOptionalOptionaldirectly on the message body
SecurityDefinitiondOptionalOptionalOptionaldirectly on the message body
SecurityDefinitionRequestcOptionalOptionalOptionaldirectly on the message body
SecurityDefinitionUpdateReportBPOptionaldirectly on the message body
SecurityListyOptionalOptionalinside the SecListGrp component
SecurityListRequestxOptionalOptionaldirectly on the message body
SecurityListUpdateReportBKOptionalinside the SecLstUpdRelSymGrp component
SecurityStatusfOptionalOptionaldirectly on the message body
SecurityTypeRequestvOptionalOptionaldirectly on the message body
SecurityTypeswOptionalOptionaldirectly on the message body
SettlementInstructionsTOptionalOptionaldirectly on the message body
SettlementObligationReportBQOptionaldirectly on the message body
StreamAssignmentReportCDOptionalinside StrmAsgnRptGrp › StrmAsgnRptInstrmtGrp
StreamAssignmentReportACKCEOptionaldirectly on the message body
TradeCaptureReportAEOptionalOptionalinside the TrdCapRptSideGrp component
TradeCaptureReportAckAROptionalOptionaldirectly on the message body
TradeCaptureReportRequestADOptionalOptionaldirectly on the message body
TradeCaptureReportRequestAckAQOptionalOptionaldirectly on the message body
TradingSessionListBJOptionalinside the TrdSessLstGrp component
TradingSessionListUpdateReportBSOptionalinside the TrdSessLstGrp component
TradingSessionStatushOptionalOptionalOptionaldirectly on the message body
UserNotificationCBOptionaldirectly 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