Skip to main content
Participants may download a list of the instruments available (or reference data about them) to trade on PMX by submitting a SecurityListRequest [x] message.

Table 23: SecurityListRequest (x) message

TagField NameReq’dData TypeComments
< Standard Header >Y35 = x
320SecurityReqIDYStringUnique ID associated with this request.
336TradingSessionIDNStringUsed to filter for instruments of the specified market state:
• CLOSED
• OPEN
• PREOPEN
• SUSPENDED
• EXPIRED
• TERMINATED
• HALTED
• MATCH_AND_CLOSE_AUCTION
559SecurityListRequestTypeYintThe type of request being made.
0 = Individual symbol
4 = All Securities
55SymbolCStringRequired if SecurityListRequestType (559) = 0 (individual security)
< Standard Trailer >Y
Example 21: Request for information on all securities
8=FIXT.1.1 | 9=75 | 35=x | 49=SENDER | 56=TARGET | 34=12 | 52=20240516-14:28:38 | 320=REF-DATA-001 | 559=4 | 10=048 |
Upon receipt, PMX will respond with a SecurityList [y] message containing the requested information. Note that the content provided by the SecurityList [y] message does not differ depending on whether an individual symbol was listed versus all securities.

Table 24: SecurityList (y) message

TagField NameReq’dData TypeComments
< Standard Header >Y35 = y
320SecurityReqIDYStringThe unique SecurityReqID (320) sent on the request.
322SecurityResponseIDYStringUnique ID for this response. Typically a 13 character alphanumeric string.
560SecurityRequestResultYintThe status of the request.
0 = Valid request
1 = Invalid or unsupported request
3 = Not authorized to retrieve instrument data
146NoRelatedSymCNumInGroupNumber of instruments to be returned. Only present for valid requests.
→ 55SymbolYStringInstrument symbol
→ 48SecurityIDYStringWill always equal Symbol (55)
→ 22SecurityIDSourceYint8 = Exchange symbol
→ 167SecurityTypeNStringType of instrument
CS = Common Stock
FUT = Future
FXSPOT = FX Spot (incl. crypto)
FXSWAP = FX Swap
OOF = Options on Futures
OPT = Option
NONE = Other
→ 231ContractMultiplierNfloatThe ratio or multiplier to convert from “nominal” units (e.g. contracts) to total units (e.g. shares). Applicable for Fixed Income, Derivatives, etc.
→ 864NoEventsYNumInGroupNumber of repeating EventType entries. Will always be 1.
→→ 865EventTypeYintCode to represent the type of event
5 = Activation
→→ 866EventDateYLocalMktDateDate that the instrument first started (or will start) trading on the exchange in YYYYMMDD format.
→→ 868EventTextYStringEvent string. Always ‘StartDate’.
→ 969MinPriceIncrementYfloatMinimum price increment (tick size)
→ 1151SecurityGroupYStringThe name of the group of securities to which this instrument belongs.
→ 562MinTradeVolYQtyThe minimum quantity allowed on an order. This field can be a decimal, indicating the ability to trade fractional shares of this instrument.
→ 15CurrencyYCurrencyCurrency for the instrument, or quote currency in the case of Forex. For example, for BTC-USD, the Currency would be USD.
< Standard Trailer >Y
Example 22: SecurityList [y] indicating two securities (color-coded)
8=FIXT.1.1 | 9=336 | 35=y | 34=9 | 49=TARGET | 52=20240516-14:28:38.864954771 | 56=SENDER | 146=2 | 55=GC-Dec-2030 | 48=GC-Dec-2030 | 22=8 | 167=NONE | 231=1 | 864=1 | 865=5 | 866=19700101 | 868=StartDate | 969=0.01 | 1151=GC | 562=1 | 15=USD | 55=GOOG | 48=GOOG | 22=8 | 167=NONE | 231=1 | 864=1 | 865=5 | 866=19700101 | 868=StartDate | 969=0.01 | 1151=Equities | 562=1 | 15=USD | 320=2007026312 | 322=1HPT7F2AA6404 | 560=0 | 10=007 |

Figure 16: Request form security reference data