Skip to main content
The Security Definition d message is used for the following:
  • Accept the security defined in a Security Definition Request (c) message with changes to the definition and/or identity of the security.
  • Reject the security requested in a Security Definition Request message
TagNameTypeRequiredComments
320SecurityReqIDStringYesRequest identifier
322SecurityResponseIDstingYesEqual to the SecurityReqID
323SecurityResponseTypeintYesType of Security Definition response.

Valid values:

  • 2 = accept security proposal with possible revisions as indicated in the message,
  • 5 = reject proposal

55SymbolStringNoCommon, “human understood” representation of the security
48SecurityIDStringNoTakes precedence in identifying security to counterparty.
22SecurityIDSourceStringNo101 = Multi-cast identifier, 102 = Combo instrument identifier
225IssueDateUTCTimestampNoCreation timestamp
873DatedDateUTCTimestampNoState timestamp
58TextStringNoExplanatory text string
Group UnderlyingInstrument
711NoUnderlyingsintNoNumber of underlying items in the group, if applicable. Underlying group is present in reply to Security Definition Request (c) with SecurityRequestType(321) = 3
=>311UnderlyingSymbolStringNoCombo-instrument symbols in reply to Security Definition Request (c) with SecurityRequestType(321) = 3
965SecurityStatusStringNoDenotes the current state of the Instrument.

Valid values:

  • 1 = Active,
  • 2 = Inactive,
  • 3 = RFQ,
  • 4 = Closed,
  • 12 = Archivized

Group InstrmtLegGrp
555NoLegsintYesNumber of legs that make up the Security
=>600LegSymbolStringNoNon-combo instrument name
=>623LegRatioQtyintNoPositive or negative adjusted to the strategy definition