LowLimitPrice (FIX tag 1148)

PriceFIX 5.0 SP2

LowLimitPrice (tag 1148) is a Price field defined in FIX 5.0 SP2. It appears in 8 message types, always optionally.

At a glance

Tag
1148
Name
LowLimitPrice
Datatype
Price (float)
Dialects
FIX 5.0 SP2
Messages
8

What the specification says

Allowable low limit price for the trading day. A key parameter in validating order price. Used as the lower band for validating order prices. Orders submitted with prices below the lower limit will be rejected

Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.

A real message using tag 1148

MarketDefinition · FIX 5.0 SP2
TagFieldWire valueMeaning
8BeginStringFIXT.1.1
9BodyLength100
35MsgTypeBUMarketDefinition
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
1394MarketReportIDEXAMPLE
1301MarketIDXNAS
1148LowLimitPrice1.09210
10CheckSum074
Edit and decode it yourself

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.

Open in the full decoder →

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 1148 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.

MessageMsgTypeRequirednessWhere in the message
DerivativeSecurityListAAOptionalinside DerivativeSecurityDefinition › MarketSegmentGrp › SecurityTradingRules › BaseTradingRules › PriceLimits
DerivativeSecurityListUpdateReportBROptionalinside DerivativeSecurityDefinition › MarketSegmentGrp › SecurityTradingRules › BaseTradingRules › PriceLimits
MarketDefinitionBUOptionalinside BaseTradingRules › PriceLimits
MarketDefinitionUpdateReportBVOptionalinside BaseTradingRules › PriceLimits
SecurityDefinitiondOptionalinside MarketSegmentGrp › SecurityTradingRules › BaseTradingRules › PriceLimits
SecurityDefinitionUpdateReportBPOptionalinside MarketSegmentGrp › SecurityTradingRules › BaseTradingRules › PriceLimits
SecurityListyOptionalinside SecListGrp › SecurityTradingRules › BaseTradingRules › PriceLimits
SecurityListUpdateReportBKOptionalinside SecLstUpdRelSymGrp › SecurityTradingRules › BaseTradingRules › PriceLimits

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 1148 in TypeScript

decode.tsts
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[1148];field?.name;   // "LowLimitPrice"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a number

Other 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-fix50sp2