PutOrCall (FIX tag 201)

intFIX 4.4FIX 4.2

PutOrCall (tag 201) is an int field defined in FIX 4.4 and FIX 4.2. It appears in 59 message types, always optionally. It is an enumerated field with 2 defined values.

At a glance

Tag
201
Name
PutOrCall
Datatype
int
Dialects
FIX 4.4 and FIX 4.2
Messages
59
Valid values
2

What the specification says

FIX 4.4

Indicates whether an Option is for a put or call

FIX 4.2

Indicates whether an Option is for a put or call.

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

A real message using tag 201

NewOrderSingle · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength117
35MsgTypeDOrder – Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
201PutOrCall0Put
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
10CheckSum247
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 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.

ValueMeaningSymbolic name
0PutPUT / Put
1CallCALL / Call

Where tag 201 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.

MessageMsgTypeFIX 4.4FIX 4.2Where in the message
Advertisement7OptionalOptionalinside the Instrument component
AllocationInstructionJOptionalOptionalinside the Instrument component
AllocationReportASOptionalinside the Instrument component
AssignmentReportAWOptionalinside the Instrument component
CollateralAssignmentAYOptionalinside the Instrument component
CollateralInquiryBBOptionalinside the Instrument component
CollateralInquiryAckBGOptionalinside the Instrument component
CollateralReportBAOptionalinside the Instrument component
CollateralRequestAXOptionalinside the Instrument component
CollateralResponseAZOptionalinside the Instrument component
ConfirmationAKOptionalinside the Instrument component
CrossOrderCancelReplaceRequesttOptionalinside the Instrument component
CrossOrderCancelRequestuOptionalinside the Instrument component
DerivativeSecurityListAAOptionalinside RelSymDerivSecGrp › Instrument
DontKnowTradeQOptionalOptionalinside the Instrument component
EmailCOptionalOptionalinside InstrmtGrp › Instrument
ExecutionReport8OptionalOptionalinside the Instrument component
IOI6OptionalOptionalinside the Instrument component
ListStrikePricemOptionalOptionalinside InstrmtStrkPxGrp › Instrument
MarketDataIncrementalRefreshXOptionalOptionalinside MDIncGrp › Instrument
MarketDataRequestVOptionalOptionalinside InstrmtMDReqGrp › Instrument
MarketDataSnapshotFullRefreshWOptionalOptionalinside the Instrument component
MassQuoteiOptionalOptionalinside QuotSetGrp › QuotEntryGrp › Instrument
MassQuoteAcknowledgementbOptionalOptionalinside QuotSetAckGrp › QuotEntryAckGrp › Instrument
MultilegOrderCancelReplaceACOptionalinside the Instrument component
NewOrderCrosssOptionalinside the Instrument component
NewOrderListEOptionalOptionalinside ListOrdGrp › Instrument
NewOrderMultilegABOptionalinside the Instrument component
NewOrderSingleDOptionalOptionalinside the Instrument component
NewsBOptionalOptionalinside InstrmtGrp › Instrument
OrderCancelReplaceRequestGOptionalOptionalinside the Instrument component
OrderCancelRequestFOptionalOptionalinside the Instrument component
OrderMassCancelReportrOptionalinside the Instrument component
OrderMassCancelRequestqOptionalinside the Instrument component
OrderMassStatusRequestAFOptionalinside the Instrument component
OrderStatusRequestHOptionalOptionalinside the Instrument component
PositionMaintenanceReportAMOptionalinside the Instrument component
PositionMaintenanceRequestALOptionalinside the Instrument component
PositionReportAPOptionalinside the Instrument component
QuoteSOptionalOptionalinside the Instrument component
QuoteCancelZOptionalOptionalinside QuotCxlEntriesGrp › Instrument
QuoteRequestROptionalOptionalinside QuotReqGrp › Instrument
QuoteRequestRejectAGOptionalinside QuotReqRjctGrp › Instrument
QuoteResponseAJOptionalinside the Instrument component
QuoteStatusReportAIOptionalinside the Instrument component
QuoteStatusRequestaOptionalOptionalinside the Instrument component
RFQRequestAHOptionalinside RFQReqGrp › Instrument
RequestForPositionsANOptionalinside the Instrument component
RequestForPositionsAckAOOptionalinside the Instrument component
SecurityDefinitiondOptionalOptionalinside the Instrument component
SecurityDefinitionRequestcOptionalOptionalinside the Instrument component
SecurityListyOptionalinside SecListGrp › Instrument
SecurityListRequestxOptionalinside the Instrument component
SecurityStatusfOptionalOptionalinside the Instrument component
SecurityStatusRequesteOptionalOptionalinside the Instrument component
TradeCaptureReportAEOptionalinside the Instrument component
TradeCaptureReportAckAROptionalinside the Instrument component
TradeCaptureReportRequestADOptionalinside the Instrument component
TradeCaptureReportRequestAckAQOptionalinside the Instrument component

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

decode.tsts
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix44";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const putOrCall = message.fields[201]?.raw;// e.g. "0" — Put// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(201)  ?.enumValues?.find((e) => e.value === putOrCall)  ?.description;

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