FIX 4.4
The FIX 4.4 dictionary as shipped in @boarteam/fix-dict-fix44. Messages announce it in BeginString (tag 8) as FIX.4.4.
What it contains
How it differs
Against FIX 4.2: FIX 4.4 carries 542 fields, 47 message types and 103 components that FIX 4.2 does not define. The other way round, FIX 4.2 has 35 fields with no FIX 4.4 counterpart.
Against FIX 5.0 SP2: FIX 4.4 carries 1 message type and 2 components that FIX 5.0 SP2 does not define. The other way round, FIX 5.0 SP2 has 540 fields, 23 message types and 73 components with no FIX 4.4 counterpart.
1 message type appears only in FIX 4.4:
2 component blocks exist only in FIX 4.4: ExecsGrp, UndInstrmtStrkPxGrp.
These are presence counts only. For the renamed fields, changed datatypes and enum differences, see FIX 4.4 vs FIX 4.2 — every entity page also shows per-version presence and requiredness side by side.
Decode FIX 4.4 in TypeScript
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix44";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);message.beginString; // "FIX.4.4"issues; // FixIssue[] — never an exceptionDecode 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