MaxPriceVariation (FIX tag 1143)

floatFIX 5.0 SP2

MaxPriceVariation (tag 1143) is a float field defined in FIX 5.0 SP2. It appears in 8 message types, always optionally.

At a glance

Tag: 1143
Name: MaxPriceVariation
Datatype: float
Dialects: FIX 5.0 SP2
Messages: 8

What the specification says

The maximum price variation of an execution from one event to the next for a given security. Expressed in absolute price terms.

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

A real message using tag 1143

MarketDefinition · FIX 5.0 SP2

Tag	Field	Wire value	Meaning
8	BeginString	FIXT.1.1
9	BodyLength	96
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
1143	MaxPriceVariation	1.0
10	CheckSum	087

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 1143 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
DerivativeSecurityListUpdateReport	BR	Optional	inside DerivativeSecurityDefinition › MarketSegmentGrp › SecurityTradingRules › BaseTradingRules
MarketDefinition	BU	Optional	inside the BaseTradingRules component
MarketDefinitionUpdateReport	BV	Optional	inside the BaseTradingRules component
SecurityDefinition	d	Optional	inside MarketSegmentGrp › SecurityTradingRules › BaseTradingRules
SecurityDefinitionUpdateReport	BP	Optional	inside MarketSegmentGrp › SecurityTradingRules › BaseTradingRules
SecurityList	y	Optional	inside SecListGrp › SecurityTradingRules › BaseTradingRules
SecurityListUpdateReport	BK	Optional	inside SecLstUpdRelSymGrp › SecurityTradingRules › BaseTradingRules

Wire format

A decimal number. The wire form keeps its trailing zeros, which is why decoders expose the raw string alongside the parsed number. @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 1143 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[1143];field?.name;   // "MaxPriceVariation"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