There are some differences in handling between IQFeed and IB.
Symbols in IQFeed are completely textual and obtained through a 'mktsymbols' text file.
For IB, to generate trades and request data through their API, contract numbers are typically required. To request contract numbers for equities traded on the primary exchanges, IQFeed symbols can typically be used directly for the lookup in the IB API. For options and futures, you have to perform lookups through the IB API based upon underlying symbol, currency, expiry dates, strikes, etc... Then use that contract number to make the request through the other portions of the IB API.
If the IQFeed people have these lookup tables as another service, cool.
But for us do-it-yourselfers, code needs to be written. I have written code to parse the IQFeed market symbols text file, pull out the options/futures info, and use that to look up contract details in the IB API.
If you want to wade through a bunch of stuff I've done:
An IQFeed provider:https://github.com/rburkholder/trade-frame/tree/master/lib/TFIQFeed
An IB provider:https://github.com/rburkholder/trade-frame/tree/master/lib/TFInteractiveBrokers
Send me a message at firstname.lastname@example.org if you'd like more instructions.
All this is based upon the fact that I start with the mktsymbols file, decode it, and use it to request data from IQFeed, and to generate trades with IB. To go the other way around, if you have IB contract info, I have some other code in the same repository which will build IQFeed symbols from contract info and underlying symbol names. There are some futures and options underlying symbol which require a manually composed lookup table, such as GC in InteractiveBrokers and QGC in IQFeed.Edited by stargrazer on Mar 21, 2017 at 03:41 AM