Finding Derivative Products
Both examples above yielded instruments that are referenced by derivative products, though these endpoints intentionally omit those results for simplicity.
However, if we want to find those derivatives, we start with a more general-purpose endpoint that identifies the relationships between underliers and their derivatives:
GET /iserver/secdef/search
Consider the following example workflow to locate ES futures options.
Step 1, Obtaining Index Conid and Contract Months
First, we’ll want to capture the conid of the underlying ES index. This index conid can be stored and reused in the future to fetch derivative products as needed.
GET https://api.ibkr.com/v1/api/iserver/secdef/search?symbol=ES&secType=FUT
From this response we should capture these values:
- The index’s conid (“conid”:“11004958”)
- From the “FOP” object, the semicolon-separated list of futures options Contract Months (“months”:“DEC24;MAR25;JUN25;DEC25;DEC26;DEC27;DEC28”)
- The index’s exchange, “CME”
Step 2, Obtaining Futures Options Conids
Next we collect the following parameters.
Conidof underlying index (conid=11004968for ES)- Name of the exchange (
exchange=CME) - Security Type of the instruments we’re seeking (
sectype=FOP, recalling that CME Event Contracts are modeled as futures options) - Contract Month of interest, which restricts the scope of the query
And make the following request to obtain records instrument records, including conids, for ES futures options in the DEC24 contract month:
GET /iserver/secdef/info?conid=11004968&exchange=CME§ype=FOP&month=DEC24

