Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

The Security List message is the response to the Security List Request GET message. It returns the list of Instruments that matches the criteria you specified in the request.

Request parameters

Field Name

Format

Req'd

Comments

MsgType

String

Identifies the message type

MsgSeqNum

SeqNum

Incremental number used to identify if receiver missed a message

SendingTime

UTCTimestamp

Time of sending this message

David Matraberci : These above should not be in the sheet, as they are part of the standard header

SecurityReportID

Int

Unique identifier

ClearingBusinessDate

LocalMktDate

E.g.: 20220818

SecurityListDesc

String

All SWAP/Lend traded Instruments with BTC/USD as underlying

David Matraberci : This might be an overkill/duplicate to generate the text as well as the message?

SecurityRequestResult

Int

0 = Valid request;
1 = Invalid or unsupported request;
2 = No instruments found that match

TransactTime

UTCTimestamp

20220818-14:18:21.123

TotNoRelatedSym

Int

Total number of Instruments being returned for this request.

MarketID

Exchange

XCDE

MarketSegmentID

String

SWAP/Lend

Component block

<SecListGrp>

>

NoRelatedSym

Int

Number of Instrument in that response

David Matraberci : As this is not used in FIXML, I’d suggest to drop from here as well, it normally has a technical reason to use a number for reading the stream.

Component block

<Instrument>

Repeating group

>>

Symbol

String

E.g.: BTC/USD-ID-R

>>

Product

Int

13 = Financing (Repo is a financing product)

>>

SecurityGroup

String

ID = Intra-day;
ON = Overnight;
TOD-TOM = Today + 1 day during week-end;
1w = 1 week
2w = 2 weeks

>>

SecurityType

String

REPO

>>

MaturityDate

LocalMktDate

20220822 (Settle date of Far_Leg)

>>

MaturityTime

TZTimeOnly

20220822-17:00-05 (for 5pm NY on Aug22)

David Matraberci : Is this required?

>>

SecurityStatus

String

1 = Active;

2 = Inactive

David Matraberci : Inactive requires feature

>>

MinPriceIncrement

Float

0.01

David Matraberci : TBD how to get this data

>>

SettlMethod

Char

P = Physical settlement required

>>

SecurityDesc

String

BTC/USD Intra-day Repo

Component block

<FinancingDetails>

>>

DeliveryType

Int

0 = "Versus Payment": Deliver (if sell) or Receive (if buy) vs. (against) Payment

Component block

<SecurityTradingRules>

Component block

<BaseTradingRules>

>>>

ExpirationCycle

Int

0 = Expire on trading session close

>>>

MinTradeVol

Qty

E.g: 1 = minimum order quantity that can be submitted

David Matraberci : Where is this coming from? I guess it will be different for BTC and ADA

>>>

PriceType

Int

6 = Spread

Component block

<UndInstrmtGrp>

Component block

<UnderlyingInstrument>

Must be provided if Number of underlyings > 0

>>>

UnderlyingSymbol

String

BTC/USD

>>>

UnderlyingProduct

Int

100 = CRYPTO (not yet a FIX Protocol standard value)

>>>

UnderlyingSecurityType

String

CRYPTOCASH

>>>

UnderlyingSecurityDesc

String

BTC/USD Cash

>

Currency

USD = the currency this Repo is priced in (terms currency)

Component block

<InstrmtLegSecListGrp>

>>

NoLegs

2 (always 2 for a Repo)

David Matraberci : I am not sure if this is required, as this is not a FIX message

Component block

<InstrumentLeg>

Description of the first leg of this Repo

>>>

LegSymbol

String

BTC/USD-CASH

>>>

LegSecurityDesc

String

BTC/USD Cash

>>>

LegRatioQty

Float

1

>>>

LegSide

Int

2 = SELL

>>>

LegCurrency

Currency

USD

>>>

LegSettlType

Char

1 = Cash (immediate settlement)

InstrumentLeg

Description of the second leg of this Repo

David Matraberci : I believe this orange block is not required, its just a duplicate of the previous set, and should be explained there instead

LegSymbol

String

BTC/USD-Spot

LegSecurityDesc

String

BTC/USD Spot

LegRatioQty

Float

1

LegSide

Int

1 = BUY

LegCurrency

Currency

USD

LegSettlType

Char

0 = Spot (regular End-of-Day settlement)

>>

Text

String

Comment, instructions, or other identifying information.

Example missing

  • No labels