MessageEncoding (FIX tag 347)
MessageEncoding (tag 347) is a String field defined in FIX 4.4 and FIX 4.2. It belongs to the session envelope: every FIX 4.4 message carries it, so it identifies the session rather than describing the business event. It is an enumerated field with 4 defined values.
At a glance
- Tag
- 347
- Name
- MessageEncoding
- Datatype
- String
- Dialects
- FIX 4.4 and FIX 4.2
- Messages
- 93
- Valid values
- 4
What the specification says
Type of message encoding (non-ASCII (non-English) characters) used in a message’s "Encoded" fields.
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 347
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIX.4.4 | |
| 9 | BodyLength | 127 | |
| 35 | MsgType | D | Order – Single |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 347 | MessageEncoding | ISO-2022-JP | JIS |
| 11 | ClOrdID | ORD-10042 | |
| 54 | Side | 1 | Buy |
| 60 | TransactTime | 20240101-12:00:00.000 | |
| 40 | OrdType | 1 | Market |
| 10 | CheckSum | 120 |
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.
Valid values
A value outside this list is not a parse error — the message still decodes — but validate() reports it as validate/value-not-in-enum.
| Value | Meaning | Symbolic name |
|---|---|---|
| ISO-2022-JP | JIS | JIS / ISO2022JP |
| EUC-JP | EUC | EUC / EUCJP |
| Shift_JIS | for using SJIS | FOR_USING_SJIS / ShiftJIS |
| UTF-8 | Unicode | UNICODE / UTF8 |
Where tag 347 appears
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 347 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 messageEncoding = message.fields[347]?.raw;// e.g. "ISO-2022-JP" — JIS// The dictionary also carries the labels:const label = fix.dictionary .fieldByTag(347) ?.enumValues?.find((e) => e.value === messageEncoding) ?.description;Other String fields
- 337ContraTrader
- 336TradingSessionID
- 335TradSesReqID
- 324SecurityStatusReqID
- 322SecurityResponseID
- 372RefMsgType
- 320SecurityReqID
- 375ContraBroker
- 376ComplianceID
- 379BusinessRejectRefID
- 312UnderlyingSymbolSfx
- 311UnderlyingSymbol
- 310UnderlyingSecurityType
- 309UnderlyingSecurityID
- 307UnderlyingSecurityDesc
- 306UnderlyingIssuer
- 305UnderlyingSecurityIDSource
- 390BidID
- 391ClientBidID
- 302QuoteSetID
- 392ListName
- 299QuoteEntryID
- 400BidDescriptor
- 289MDEntrySeller
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