HighLimitPrice (FIX tag 1149)

PriceFIX 5.0 SP2

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

At a glance

Tag: 1149
Name: HighLimitPrice
Datatype: Price (float)
Dialects: FIX 5.0 SP2
Messages: 8

What the specification says

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

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

A real message using tag 1149

MarketDefinition · FIX 5.0 SP2

Tag	Field	Wire value	Meaning
8	BeginString	FIXT.1.1
9	BodyLength	100
35	MsgType	BU	MarketDefinition
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
1394	MarketReportID	EXAMPLE
1301	MarketID	XNAS
1149	HighLimitPrice	1.09210
10	CheckSum	075

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 1149 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
DerivativeSecurityList	AA	Optional	inside DerivativeSecurityDefinition › MarketSegmentGrp › SecurityTradingRules › BaseTradingRules › PriceLimits
DerivativeSecurityListUpdateReport	BR	Optional	inside DerivativeSecurityDefinition › MarketSegmentGrp › SecurityTradingRules › BaseTradingRules › PriceLimits
MarketDefinition	BU	Optional	inside BaseTradingRules › PriceLimits
MarketDefinitionUpdateReport	BV	Optional	inside BaseTradingRules › PriceLimits
SecurityDefinition	d	Optional	inside MarketSegmentGrp › SecurityTradingRules › BaseTradingRules › PriceLimits
SecurityDefinitionUpdateReport	BP	Optional	inside MarketSegmentGrp › SecurityTradingRules › BaseTradingRules › PriceLimits
SecurityList	y	Optional	inside SecListGrp › SecurityTradingRules › BaseTradingRules › PriceLimits
SecurityListUpdateReport	BK	Optional	inside 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 1149 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[1149];field?.name;   // "HighLimitPrice"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a number

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

Try the decoder Source on GitHub