MDEntryPx (FIX tag 270)
MDEntryPx (tag 270) is a Price field defined in FIX 4.4 and FIX 4.2. It appears in 2 message types, always optionally.
At a glance
- Tag
- 270
- Name
- MDEntryPx
- Datatype
- Price (float)
- Dialects
- FIX 4.4 and FIX 4.2
- Messages
- 2
What the specification says
Price of the Market Data Entry.
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 270
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIX.4.4 | |
| 9 | BodyLength | 105 | |
| 35 | MsgType | W | Market Data-Snapshot/Full Refresh |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 268 | NoMDEntries2 entries | 2 | repeating group |
| 269 | MDEntryType | 0 | Bid |
| 270 | MDEntryPx | 1.09210 | |
| 269 | MDEntryType | 0 | Bid |
| 270 | MDEntryPx | 1.09210 | |
| 10 | CheckSum | 148 |
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.
Where tag 270 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 | Where in the message |
|---|---|---|---|---|
| MarketDataIncrementalRefresh | X | Conditional | Optional | inside the MDIncGrp component |
| MarketDataSnapshotFullRefresh | W | Conditional | Required | inside the MDFullGrp component |
Wire format
A decimal price. Precision is a venue convention, not a protocol rule, so compare the raw string when exactness matters. @boarteam/fix parses the value as a number and reports parse/invalid-float when it does not lex as one; the raw string is kept so precision and trailing zeros are never lost.
Read tag 270 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 field = message.fields[270];field?.name; // "MDEntryPx"field?.raw; // the verbatim wire stringfield?.value; // coerced to a numberOther Price 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