FIX protocol reference
Every tag, message, component and datatype in FIX 4.4 and FIX 4.2 — 947 fields, 93 message types, 105 components, 26 datatypes. Each page carries a real message, decoded when the page was built, that you can edit and re-decode in your browser.
Browse
Frequently looked up
How this reference is built
Everything here is generated from the dictionaries shipped in @boarteam/fix-dict-fix44 and -fix42. Structure comes from the QuickFIX data dictionaries and the FIX Repository; field, enum and datatype descriptions come from the Apache-2.0 FIX Orchestra sources. Nothing is scraped, and the decoded example on every page is produced by running @boarteam/fix at build time — if an example stopped parsing, the build would fail rather than publish it.
Where FIX 4.4 and FIX 4.2 disagree — a renamed field, a different datatype, a value added or dropped, a field that is optional in one and required in the other — both are shown. See FIX 4.4 vs FIX 4.2, dictionary coverage, and licences & attribution.