OrderRestrictions (FIX tag 529)
OrderRestrictions (tag 529) is a MultipleValueString field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 11 message types, always optionally. It is an enumerated field with 10 defined values.
At a glance
- Tag
- 529
- Name
- OrderRestrictions
- Datatype
- MultipleValueString (String)
- Dialects
- FIX 4.4 and FIX 5.0 SP2
- Messages
- 11
- Valid values
- 10
What the specification says
Restrictions associated with an order. If more than one restriction is applicable to an order, this field can contain multiple instructions separated by space.
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 529
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIX.4.4 | |
| 9 | BodyLength | 117 | |
| 35 | MsgType | D | Order – Single |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 11 | ClOrdID | ORD-10042 | |
| 54 | Side | 1 | Buy |
| 60 | TransactTime | 20240101-12:00:00.000 | |
| 40 | OrdType | 1 | Market |
| 529 | OrderRestrictions | 1 | Program Trade |
| 10 | CheckSum | 005 |
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.
Valid values
A value outside this list is not a parse error — the message still decodes — but validate() reports it as validate/value-not-in-enum.
| Value | Meaning | Symbolic name | Dialects |
|---|---|---|---|
| 1 | Program Trade | PROGRAM_TRADE | FIX 4.4, FIX 5.0 SP2 |
| 2 | Index Arbitrage | INDEX_ARBITRAGE | FIX 4.4, FIX 5.0 SP2 |
| 3 | Non-Index Arbitrage | NON_INDEX_ARBITRAGE | FIX 4.4, FIX 5.0 SP2 |
| 4 | Competing Market Maker | COMPETING_MARKET_MAKER | FIX 4.4, FIX 5.0 SP2 |
| 5 | Acting as Market Maker or Specialist in the security | ACTING_AS_MARKET_MAKER_OR_SPECIALIST_IN_THE_SECURITY | FIX 4.4, FIX 5.0 SP2 |
| 6 | Acting as Market Maker or Specialist in the underlying security of a derivative security | ACTING_AS_MARKET_MAKER_OR_SPECIALIST_IN_THE_UNDERLYING_SECURITY_OF_A_DERIVATIVE_SECURITY | FIX 4.4, FIX 5.0 SP2 |
| 7 | Foreign Entity (of foreign government or regulatory jurisdiction) | FOREIGN_ENTITY | FIX 4.4, FIX 5.0 SP2 |
| 8 | External Market Participant | EXTERNAL_MARKET_PARTICIPANT | FIX 4.4, FIX 5.0 SP2 |
| 9 | External Inter-connected Market Linkage | EXTERNAL_INTER_CONNECTED_MARKET_LINKAGE | FIX 4.4, FIX 5.0 SP2 |
| A | Riskless Arbitrage | RISKLESS_ARBITRAGE | FIX 4.4, FIX 5.0 SP2 |
| B | Issuer Holding | ISSUER_HOLDING | FIX 5.0 SP2 |
| C | Issue Price Stabilization | ISSUE_PRICE_STABILIZATION | FIX 5.0 SP2 |
| D | Non-algorithmic | NON_ALGORITHMIC | FIX 5.0 SP2 |
| E | Algorithmic | ALGORITHMIC | FIX 5.0 SP2 |
| F | Cross | CROSS | FIX 5.0 SP2 |
Where tag 529 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 5.0 SP2 | Where in the message |
|---|---|---|---|---|
| Confirmation | AK | Optional | Optional | inside the CpctyConfGrp component |
| CrossOrderCancelReplaceRequest | t | Optional | Optional | inside the SideCrossOrdModGrp component |
| ExecutionReport | 8 | Optional | Optional | directly on the message body |
| MassQuote | i | — | Optional | inside QuotSetGrp › QuotEntryGrp |
| MassQuoteAcknowledgement | b | — | Optional | inside QuotSetAckGrp › QuotEntryAckGrp |
| MultilegOrderCancelReplace | AC | Optional | Optional | directly on the message body |
| NewOrderCross | s | Optional | Optional | inside the SideCrossOrdModGrp component |
| NewOrderList | E | Optional | Optional | inside the ListOrdGrp component |
| NewOrderMultileg | AB | Optional | Optional | directly on the message body |
| NewOrderSingle | D | Optional | Optional | directly on the message body |
| OrderCancelReplaceRequest | G | Optional | Optional | directly on the message body |
| Quote | S | — | Optional | directly on the message body |
| QuoteRequest | R | — | Optional | directly on the message body |
| QuoteResponse | AJ | — | Optional | directly on the message body |
| QuoteStatusReport | AI | — | Optional | directly on the message body |
| TradeCaptureReport | AE | Optional | Optional | inside the TrdCapRptSideGrp component |
| TradeCaptureReportAck | AR | Optional | Optional | directly on the message body |
Wire format
Several values in one field, separated by spaces. Decoders return an array. @boarteam/fix splits the value on its delimiter and returns an array of strings.
Read tag 529 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 orderRestrictions = message.fields[529]?.raw;// e.g. "1" — Program Trade// The dictionary also carries the labels:const label = fix.dictionary .fieldByTag(529) ?.enumValues?.find((e) => e.value === orderRestrictions) ?.description;Other MultipleValueString 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