MaxPriceLevels (FIX tag 1090)
MaxPriceLevels (tag 1090) is an int field defined in FIX 5.0 SP2. It appears in 8 message types, always optionally.
At a glance
- Tag
- 1090
- Name
- MaxPriceLevels
- Datatype
- int
- Dialects
- FIX 5.0 SP2
- Messages
- 8
What the specification says
Allows an order to specify a maximum number of price levels to trade through. Only valid for aggressive orders and during continuous (autoexecution) trading sessions. Property lost when order is put on book. A partially filled order is assigned last trade price as limit price. Non-filled order behaves as ordinary Market or Limit.
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 1090
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIXT.1.1 | |
| 9 | BodyLength | 118 | |
| 35 | MsgType | D | NewOrderSingle |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 11 | ClOrdID | ORD-10042 | |
| 1090 | MaxPriceLevels | 1 | |
| 54 | Side | 1 | Buy |
| 60 | TransactTime | 20240101-12:00:00.000 | |
| 40 | OrdType | 1 | Market |
| 10 | CheckSum | 126 |
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 5.0 SP2 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.
Where tag 1090 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 | Requiredness | Where in the message |
|---|---|---|---|
| CrossOrderCancelReplaceRequest | t | Optional | directly on the message body |
| ExecutionReport | 8 | Optional | directly on the message body |
| MultilegOrderCancelReplace | AC | Optional | directly on the message body |
| NewOrderCross | s | Optional | directly on the message body |
| NewOrderList | E | Optional | inside the ListOrdGrp component |
| NewOrderMultileg | AB | Optional | directly on the message body |
| NewOrderSingle | D | Optional | directly on the message body |
| OrderCancelReplaceRequest | G | Optional | directly on the message body |
Wire format
A whole number, optionally signed. Leading zeros are legal on the wire and are preserved in the raw value. @boarteam/fix parses the value as a number and reports parse/invalid-int when it does not lex as one; the raw string is kept either way.
Read tag 1090 in TypeScript
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix50sp2";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const field = message.fields[1090];field?.name; // "MaxPriceLevels"field?.raw; // the verbatim wire stringfield?.value; // coerced to a numberOther int fields
- 1094PegPriceType
- 1070MDQuoteType
- 1064UnderlyingInstrumentPartySubIDType
- 1061UnderlyingInstrumentPartyRole
- 1119RootPartyRole
- 1122RootPartySubIDType
- 1054InstrumentPartySubIDType
- 1051InstrumentPartyRole
- 1043CollApplType
- 1144ImpliedMarketIndicator
- 1034DeskTypeSource
- 1032OrderHandlingInstSource
- 1152LegNumber
- 1153SettlementCycleNo
- 1024MDOriginType
- 1156ApplExtID
- 1023MDPriceLevel
- 1021MDBookType
- 1159SettlObligMode
- 1013SideTrdRegTimestampType
- 1167QuoteEntryStatus
- 1168TotNoCxldQuotes
- 1169TotNoAccQuotes
- 1170TotNoRejQuotes
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-fix50sp2