EncodedText (FIX tag 355)

dataFIX 4.4FIX 4.2FIX 5.0 SP2

EncodedText (tag 355) is a data field defined in FIX 4.4, FIX 4.2 and FIX 5.0 SP2. It appears in 71 message types, always optionally. It is length-prefixed — tag 354 carries the byte count, so the value may contain the SOH separator without breaking the message.

At a glance

Tag: 355
Name: EncodedText
Datatype: data
Dialects: FIX 4.4, FIX 4.2 and FIX 5.0 SP2
Messages: 71
Length field: tag 354

What the specification says

FIX 4.4

Encoded (non-ASCII characters) representation of the Text (58) field in the encoded format specified via the MessageEncoding (347) field. If used, the ASCII (English) representation should also be specified in the Text field.

FIX 4.2

Encoded (non-ASCII characters) representation of the Text field in the encoded format specified via the MessageEncoding field. If used, the ASCII (English) representation should also be specified in the Text field.

FIX 5.0 SP2

Encoded representation of the Text(58) field in the encoded format specified via the MessageEncoding(347) field

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

A real message using tag 355

NewOrderSingle · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	129
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
354	EncodedTextLen	7
355	EncodedText	EXAMPLE
10	CheckSum	241

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 355 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	FIX 4.4	FIX 4.2	FIX 5.0 SP2	Where in the message
Advertisement	7	Conditional	Optional	Optional	directly on the message body
AllocationInstruction	J	Conditional	Optional	Optional	directly on the message body
AllocationInstructionAck	P	Conditional	Optional	Optional	directly on the message body
AllocationInstructionAlert	BM	—	—	Optional	directly on the message body
AllocationReport	AS	Conditional	—	Optional	directly on the message body
AllocationReportAck	AT	Conditional	—	Optional	directly on the message body
ApplicationMessageReport	BY	—	—	Optional	directly on the message body
ApplicationMessageRequest	BW	—	—	Optional	directly on the message body
ApplicationMessageRequestAck	BX	—	—	Optional	directly on the message body
AssignmentReport	AW	Conditional	—	Optional	directly on the message body
BidRequest	k	Conditional	Optional	Optional	directly on the message body
BidResponse	l	Conditional	Optional	Optional	inside the BidCompRspGrp component
BusinessMessageReject	j	Conditional	Optional	Optional	directly on the message body
CollateralAssignment	AY	Conditional	—	Optional	directly on the message body
CollateralInquiry	BB	Conditional	—	Optional	directly on the message body
CollateralInquiryAck	BG	Conditional	—	Optional	directly on the message body
CollateralReport	BA	Conditional	—	Optional	directly on the message body
CollateralRequest	AX	Conditional	—	Optional	directly on the message body
CollateralResponse	AZ	Conditional	—	Optional	directly on the message body
Confirmation	AK	Conditional	—	Optional	directly on the message body
ConfirmationAck	AU	Conditional	—	Optional	directly on the message body
ConfirmationRequest	BH	Conditional	—	Optional	directly on the message body
ContraryIntentionReport	BO	—	—	Optional	directly on the message body
CrossOrderCancelReplaceRequest	t	Conditional	—	Optional	inside the SideCrossOrdModGrp component
CrossOrderCancelRequest	u	Conditional	—	Optional	inside the SideCrossOrdCxlGrp component
DerivativeSecurityList	AA	Conditional	—	Optional	inside the RelSymDerivSecGrp component
DerivativeSecurityListRequest	z	Conditional	—	Optional	directly on the message body
DerivativeSecurityListUpdateReport	BR	—	—	Optional	inside the RelSymDerivSecUpdGrp component
DontKnowTrade	Q	Conditional	Optional	Optional	directly on the message body
Email	C	Conditional	Optional	Optional	inside the LinesOfTextGrp component
ExecutionAcknowledgement	BN	—	—	Optional	directly on the message body
ExecutionReport	8	Conditional	Optional	Optional	directly on the message body
IOI	6	Conditional	Optional	Optional	directly on the message body
ListCancelRequest	K	Conditional	Optional	Optional	directly on the message body
ListExecute	L	Conditional	Optional	Optional	directly on the message body
ListStatus	N	Conditional	Optional	Optional	inside the OrdListStatGrp component
ListStatusRequest	M	Conditional	Optional	Optional	directly on the message body
ListStrikePrice	m	Optional	Optional	Optional	inside the UndInstrmtStrkPxGrp component
Logon	A	—	—	Optional	directly on the message body
Logout	5	Conditional	Optional	Optional	directly on the message body
MarketDataIncrementalRefresh	X	Conditional	Optional	Optional	inside the MDIncGrp component
MarketDataRequestReject	Y	Conditional	Optional	Optional	directly on the message body
MarketDataSnapshotFullRefresh	W	Conditional	Optional	Optional	inside the MDFullGrp component
MarketDefinition	BU	—	—	Optional	directly on the message body
MarketDefinitionUpdateReport	BV	—	—	Optional	directly on the message body
MassQuoteAcknowledgement	b	Conditional	—	Optional	directly on the message body
MultilegOrderCancelReplace	AC	Conditional	—	Optional	directly on the message body
NewOrderCross	s	Conditional	—	Optional	inside the SideCrossOrdModGrp component
NewOrderList	E	Conditional	Optional	Optional	inside the ListOrdGrp component
NewOrderMultileg	AB	Conditional	—	Optional	directly on the message body
NewOrderSingle	D	Conditional	Optional	Optional	directly on the message body
News	B	Conditional	Optional	Optional	inside the LinesOfTextGrp component
OrderCancelReject	9	Conditional	Optional	Optional	directly on the message body
OrderCancelReplaceRequest	G	Conditional	Optional	Optional	directly on the message body
OrderCancelRequest	F	Conditional	Optional	Optional	directly on the message body
OrderMassActionReport	BZ	—	—	Optional	directly on the message body
OrderMassActionRequest	CA	—	—	Optional	directly on the message body
OrderMassCancelReport	r	Conditional	—	Optional	directly on the message body
OrderMassCancelRequest	q	Conditional	—	Optional	directly on the message body
PositionMaintenanceReport	AM	Conditional	—	Optional	directly on the message body
PositionMaintenanceRequest	AL	Conditional	—	Optional	directly on the message body
PositionReport	AP	Conditional	—	Optional	directly on the message body
Quote	S	Conditional	—	Optional	directly on the message body
QuoteRequest	R	Conditional	—	Optional	directly on the message body
QuoteRequestReject	AG	Conditional	—	Optional	directly on the message body
QuoteResponse	AJ	Conditional	—	Optional	directly on the message body
QuoteStatusReport	AI	Conditional	—	Optional	directly on the message body
Reject	3	Conditional	Optional	Optional	directly on the message body
RequestForPositions	AN	Conditional	—	Optional	directly on the message body
RequestForPositionsAck	AO	Conditional	—	Optional	directly on the message body
SecurityDefinition	d	Conditional	Optional	Optional	directly on the message body
SecurityDefinitionRequest	c	Conditional	Optional	Optional	directly on the message body
SecurityDefinitionUpdateReport	BP	—	—	Optional	directly on the message body
SecurityList	y	Conditional	—	Optional	inside the SecListGrp component
SecurityListRequest	x	Conditional	—	Optional	directly on the message body
SecurityListUpdateReport	BK	—	—	Optional	inside the SecLstUpdRelSymGrp component
SecurityStatus	f	Conditional	—	Optional	directly on the message body
SecurityTypeRequest	v	Conditional	—	Optional	directly on the message body
SecurityTypes	w	Conditional	—	Optional	directly on the message body
SettlementInstructions	T	Conditional	—	Optional	directly on the message body
SettlementObligationReport	BQ	—	—	Optional	directly on the message body
StreamAssignmentReport	CD	—	—	Optional	inside StrmAsgnRptGrp › StrmAsgnRptInstrmtGrp
StreamAssignmentReportACK	CE	—	—	Optional	directly on the message body
TradeCaptureReport	AE	Conditional	—	Optional	inside the TrdCapRptSideGrp component
TradeCaptureReportAck	AR	Conditional	—	Optional	directly on the message body
TradeCaptureReportRequest	AD	Conditional	—	Optional	directly on the message body
TradeCaptureReportRequestAck	AQ	Conditional	—	Optional	directly on the message body
TradingSessionList	BJ	—	—	Optional	inside the TrdSessLstGrp component
TradingSessionListUpdateReport	BS	—	—	Optional	inside the TrdSessLstGrp component
TradingSessionStatus	h	Conditional	Optional	Optional	directly on the message body
UserNotification	CB	—	—	Optional	directly on the message body

Wire format

Raw bytes, length-prefixed by a partner field. The value may legally contain the SOH separator, which is why the length matters. @boarteam/fix reads the partner length field first and takes exactly that many bytes, so an embedded separator does not truncate the value.

Read tag 355 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);// Length-prefixed: tag 354 carries the byte count, so the// value may contain the SOH separator without breaking the message.const length = message.fields[354]?.value;const encodedText = message.fields[355]?.raw;

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 decoder Source on GitHub