Skip to main content
Version: Staging

Drop Receive FIX Spec

This document describes the SpiderRock Drop Receive FIX Gateway. This SpiderRock FIX gateway allows a client to report a clients executions and/or positions for order marking and risk purposes.

This document is intended to be used in conjunction with the SpiderRock FIX Session Guide which describes session level message handling and other SpiderRock FIX conventions in more detail.

Application Messages

Execution Report

FIX TagFIX Tag NametypeReq'dvaluesassociated record value
(SpdrAwayExecution)
comment
Standard HeaderYMsgType = 8
5020SRAccntstringYaccntEither SRAccnt or Account is required
1AccountstringYaccnt
5022SRClientFirmstringYclientFirmSR client firm. A default may be configured
11ClOrdIDstringclientOrderIdclient order ID (should be unique)
17ExecIDstringYorigExecID
lastExecID
19ExecRefIDstringYmost recent execution ID
60TransactTimeutcTimestampNfillTransactDttm
fillDttm
transaction date/time as reported by exchange or down stream broker
5036SRUsernamestringNmodifiedByuser name associated with the parent order
32LastQtyintYfillQuantity
31LastPxfloatYfillPrice
30LastMktenumNfillExch
58TextstringNcomment
150ExecTypeenumY2-Fill
1-PartialFill
F-Trade
H-TradeCxl
G-TradeCorrect
38OrderQtyintNchildSize
54SideenumY1=Buy
2=Sell
5=Sell Short
6=Sell Short Exempt
fillSide
ssaleFlag
77PositionEffectenumNO=Open
C=Close
positionType
55SymbolstringYsecKeySymbol for the position report
65SymbolSfxstringNsecKeySuffix of the symbol for the position report
207SecurityExchangestringYsecKeySee Fix Session Guide, Appendix A
55SymbolstringYsecKeyStocks, Options, Futures
Symbol for the position report
65SymbolSfxstringYsecKeyStocks
Suffix of the symbol for the position report
541MaturityDatestringYsecKeyFutures, Options
Used to specify a maturity date YYYYMMDD
202StrikePricefloatYsecKeyOptions
Strike price of the security
201PutOrCallenumN0-Put
1-Call
secKeyOptions
200MaturityMonthYearstringNsecKeyFutures, Options
The month and year of maturity YYYYMM
205MaturityDayintN1-31secKeyFutures, Options
Can be used in conjunction with MaturityMonthYear to specify a particular maturity date
167SecurityTypeenumYMLEG-MultiLeg
CS-Common Stock
FUT-Future
OPT-Option
secType
5290SRUserData1stringNuserData1client supplied data field
5291SRUserData2stringNuserData2client supplied data field

Normally there is no response to this message. In some cases, the Reject<3> or Business Reject Message<j> message will be returned if the message cannot be properly processed.

Aggregated Group Position Report

SpiderRock FIX gateway implements a user defined message to update a firm’s position for order marking and risk purposes.

There is no acknowledged response for this message. An invalid message may reject with a Session or Business level Reject.

The total position for a firm is calculated as a combination of:

  • Start of day positions known by SpiderRock (for example a spreadsheet from a clearing firm)
  • Executed Fill Quantities executed by SpiderRock
  • Open Order Quantities on orders issued by SpiderRock
  • Executed Fill Quantities Execution Reports dropped to SpiderRock
  • Aggregated Group Position Report Data

A firm may use all methods (start of day files, aggregation reports, and dropped executions) to report their positions.

The start of day position and daily bought/sold quantities may be omitted or set to zero. Care must be taken not to double-count fills. For example, a new traded quantity should not be reported on both the aggregated group position report and as a dropped fill, nor should a fill from SpiderRock be dropped back to SpiderRock.

The ClientID<109> and AggregationGroup<5701> values may be configured by SpiderRock by FIX session.

FIX TagFIX Tag NametypeReq'dvaluesassociated record value
(ExternAggGroupReport)
comment
Standard HeaderYMsgType = UAG
721PosMaintRptIdlongNUnique identifier for this position report
109ClientIDstringYpkey.clientFirmA SpiderRock supplied value
5708AggregationGroupstringYpkey.aggGroupSpiderRock supplied value
5701OpenPositionQuantityintNopenPositionStart of day position for all accounts - may be positive (long) or negative (short)
5702OpenPositionQuantityShortintNopenPositionShort start-of-day position for all accounts - must be positive if specified
5703OpenPositionTypeenumY1=Exact (default)
2=Truncated
openPosType
5704BoughtQuantityintNbotQuantityQuantity bought today. Cannot be negative
5705SoldQuantityintNsldQuantityQuantity sold today. Cannot be negative
5706BidLeavesintNbidLeavesCurrent open quantity (buy). Cannot be negative
5707AskLeavesNintaskLeavesCurrent open quantity (sell). Cannot be negative
779LastUpdateTimeutcTimestampYtimestampTimestamp of last update to date item
55SymbolstringYsecKeySymbol for the position report
65SymbolSfxstringNsecKeySuffix of the symbol for the position report
207SecurityExchangestringYsecKeySee Fix Session Guide, Appendix A
55SymbolstringYsecKeyStocks, Options, Futures
Symbol for the position report
65SymbolSfxstringYsecKeyStocks
Suffix of the symbol for the position report
541MaturityDatestringYsecKeyFutures, Options
Used to specify a maturity date YYYYMMDD
202StrikePricefloatYsecKeyOptions
Strike price of the security
201PutOrCallenumN0-Put
1-Call
secKeyOptions
200MaturityMonthYearstringNsecKeyFutures, Options
The month and year of maturity YYYYMM
205MaturityDayintN1-31secKeyFutures, Options
Can be used in conjunction with MaturityMonthYear to specify a particular maturity date
167SecurityTypeenumYMLEG-MultiLeg
CS-Common Stock
FUT-Future
OPT-Option
secType

Normally there is no response to this message. In some cases, the Reject<3> or Business Reject Message<j> message will be returned if the message cannot be properly processed.

XML Messages

SpiderRock FIX Drop Receive Gateway allows an execution report or a aggregation report to be submitted as an XML formatted FIX message.

FIX TagFIX Tag NametypeReq'dvaluesassociated record value
(ExternAggGroupReport)
comment
Standard HeaderYMsgType = n
212XmlDataLenintNignored
213XmlDatastringYShould not contain embedded SOH characters. Use '|' to delimit FIX fields

Valid XmlData must contain a message body conforming to an Execution Report or Aggregated Group Position Report, above.

Normally there is no response to this message. In some cases, the Reject<3> or Business Reject Message<j> message will be returned if the message cannot be properly processed.