Join the 80,000 other DTN customers who enjoy the fastest, most reliable data available. There is no better value than DTN!

(Move your cursor to this area to pause scrolling)




"I would just like to say that IQFeed version 4 is running very well and I am very happy with its performance. I would also like to extend a big thanks for the fast and efficient help that I always receive. My questions and concerns are always addressed promptly. Way to go!" - Comment from Josh in CO.
"I just wanted to say how happy I am with your service. I was able to download the API docs last week and I was able to replicate Interactive Brokers historical bar queries and realtime bar queries over the weekend. That was about one of the fastest integrations that I've ever done and it works perfectly!!!!" - Comment from Jason via Email
"DTN has never given me problems. It is incredibly stable. In fact I've occasionally lost the data feed from Interactive Brokers, but still been able to trade because I'm getting good data from DTN." - Comment from Leighton
"Awesome response, as usual. It is a sincere and refreshing pleasure to do business with DTN, compared to your competition." - Comment from Ryan
"Thanks for the great product and support. During this week of high volume trading, my QuoteTracker + IQ Feed setup never missed a beat. Also, thanks for your swiftness in responding to data issues. I was on ******* for a few years before I made the switch over early this year, and wish I had done it a long time ago." - Comment from Ken
"Everything is working great with the API. I love it." - Comment from Calvin
"The service is great, I see a noticeable improvement in my volume profiles over [broker]'s data feed" - Comment from Larry
"Just a quick one to say I'm very impressed so far :) The documentation for developers is excellent and I've quickly managed to get an app written to do historical downloads. The system is very robust and pretty quick considering the extent of data that's available. The support guys have been very helpful too, in combination with the forums it's been plain sailing so far!" - Comment from Adam
"And by the way, have to say this. I love the IQFeed software. It's rock solid and it has a really nice API." - Comment from Thomas via RT Chat
"I am keeping IQFeed, much better reliabilty than *******. I may refer a few other people in the office to switch as well." - Comment from Don
Home  Search  Register  Login  Recent Posts

Information on DTN's Industries:
DTN Oil & Gas | DTN Trading | DTN Agriculture | DTN Weather
Follow DTNMarkets on Twitter
DTN.IQ/IQFeed on Twitter
DTN News and Analysis on Twitter
Viewing User Profile for: DTN_Gary_Stephen
About Contact
Joined: Jul 3, 2019 11:09 AM
Last Post: Yesterday @ 02:20 PM
Last Visit: Yesterday @ 04:56 PM
Website:  
Location:
Occupation:
Interests:
Avatar:
Email: gary.stephen@dtn.com
AIM:
ICQ:
MSN IM:
Yahoo IM:
Post Statistics
DTN_Gary_Stephen has contributed to 5 posts out of 19206 total posts (0.03%) in 46 days (0.11 posts per day).

20 Most recent posts:

Andrew,

First, that is from Protocol 4.9, which is the oldest active (but still default) protocol. In all later protocols, this is handled differently.

For protocol 4.9, there is an explanation here: http://www.iqfeed.net/dev/api/docs/docs51/Level1UpdateSummaryMessage.cfm

Quote: The character indicates one of the following:
t - A trade update occurred
T - Extended Trade = Any trade that is counted in volume (field 7) but does not set a new open, high, low, or last.
b - A bid update occurred (an ask update may also have occurred)
a - An ask update occurred
o - Some other type of update occurred


For later protocols, the Message Contents field contains the type of trade(s) this message reflects. As of 6.0, the explanation of the codes is:

Quote: Possible single character values include:
C - Last Qualified Trade.
E - Extended Trade = Form T trade.
O - Other Trade = Any trade not accounted for by C or E.
b - A bid update occurred.
a - An ask update occurred.
o - An Open occurred.
h - A High occurred.
l - A Low occurred.
c - A Close occurred.
s - A Settlement occurred.
v - A volume update occurred.


You can get multiple codes in a single message but you will only get one trade identifier per message. It is also possible to receive no codes in a message if the fields that updated were not trade or quote related.

Sincerely,
Gary Stephen


IQFeed Developer Support » Exchange ID vs Listed Market Yesterday @ 01:50 PM (Total replies: 3)

Andrew,

Quote: What's the difference between Exchange ID vs Listed Market in the Fundamental msg?


One is more specific than the other.

Recently, the exchanges started splitting into what can best be described as sub-exchanges. For example, what we think of as NASDAQ technically consists of several different exchanges: NCM (NASDAQ Capital Market), NGM (NASDAQ Global Market), and NGSM (NASDAQ Global Select Market), and others such as OTC and OTCBB.

In the F message, ExchangeID stores the broader group code (NASDAQ). Listed Market stores the more specific exchange code (NGSM). For example, the F message for MSFT would indicate 5 (NASDAQ) for Exchange ID and 21 (NGSM) for Listed Market. An NGM commodity would have 5 and 1, respectively.

The SLM command, as you noted, returns all the Listed Markets, and the exchange ID to which they belong:

1,NGM,Nasdaq Global Market,5,NASDAQ,
2,NCM,National Capital Market,5,NASDAQ,
3,OTC,Nasdaq other OTC,5,NASDAQ,
4,OTCBB,Nasdaq OTC Bulletin Board,5,NASDAQ,
5,NASDAQ,Nasdaq,5,NASDAQ,
6,NYSE_AMERICAN,NYSE American (Equities and Bonds),6,NYSE_AMERICAN,
7,NYSE,New York Stock Exchange,7,NYSE,
8,CHX,Chicago Stock Exchange,0,NONE,

Listed Markets 1, 2, 3, 4, and 5 are all part of Exchange ID 5. (An exchange can be part of itself.) In some cases there is no group ID, in which case that field will return 0.

The documentation seems to use the terms "Exchange ID", "Exchange Group", and "Group ID" interchangeably. They all mean the same thing: the broader definition of the exchange. We intend to edit this to make it more clear, and to explain the relationship between these terms and Listed Market.

Both the ExchangeID and Listed Market fields say "use the Listed Markets lookup to decode this value." This is correct; the list you get with SLM command consists of both.

Please note that you must specify Protocol 5.2 or later to see the exchange IDs with the SLM command. On 5.1 or the API default of 4.9, they will not be there.

Let me know if you still have any questions on this! I'll post in this thread if there are any related updates on this.

Sincerely,
Gary Stephen


IQFeed Developer Support » Exchange ID vs Listed Market Yesterday @ 09:21 AM (Total replies: 3)

Andrew,

I am investigating this now.

In the meantime, I can tell you that yes, the GroupID was added to the SLM response between protocols 5.1 and 5.2. It hasn't changed since then.

Sincerely,
Gary Stephen
DTN IQFeed API Support

Sincerely,
Gary Stephen



Saifullah,

That log entry (assuming it continues counting down to 0) means the IQFeed app is failing to connect locally. This can be caused by something interfering with the traffic. Make sure the subnet is open on the following port ranges:

66.112.156.XXX ports 5000 - 5050 and 60000 - 60050
66.112.148.XXX ports 5000 - 5050 and 60000 - 60050

Sincerely,
Gary Stephen
DTN IQFeed API Support


Sincerely,
Gary Stephen

Edited by DTN_Gary_Stephen on Aug 14, 2019 at 11:28 AM

Data and Content Support » Benchmark (Index) Prices Jul 8, 2019 09:54 AM (Total replies: 1)

Hello,

It looks like your question about the symbols was answered at http://forums.iqfeed.net/index.cfm?page=topic&topicID=5618 . However, I'd like to add a little bit to it, on how to get the weekly data via TCP/IP connection.

The TCP/IP data has a historical section, described at http://www.iqfeed.net/dev/api/docs/HistoricalviaTCPIP.cfm. It has a code to retrieve composite weekly datapoints, which is HWX. The syntax of the request is:

HWX,[Symbol],[MaxDatapoints],[DataDirection],[RequestID],[DatapointsPerSend]<CR><LF>

All but HWX and the ticker symbol are optional. The other parameters let you specify, respectively, a maximum number of data points; whether you want oldest-to-newest or newest-to-oldest (set DataDirection to 1 for the latter); RequestID (an identifier that will be sent back at the start of each line) and DatapointsPerSend (the number of datapoints that IQConnect.exe will queue before attempting to send across the socket to your app).

Gary Stephen, DTN

Sincerely,
Gary Stephen



Time: Sat August 17, 2019 3:34 PM CFBB v1.2.0 15 ms.
© AderSoftware 2002-2003