DTN IQFeed, DTN.IQ, DTN ProphetX Support Forums

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 ran your IQFeed DDE vs. my broker vs. a level II window for some slow-moving options. I would see the level II quote change, then your feed update instantaneously. My broker's DDE, however, would take as much as 30 seconds to update. I am not chasing milliseconds, but half a minute is unacceptable." - Comment from Rob

"I used to have *******, but they are way more money for the same thing. I have had no probs with data from DTN since switching over." - Comment from Public Forum Post

"Excellent datafeed !!!" - Comment from Arely

"Thanks for all of your help. Great customer service deserves to be recognized which one the reasons I've been a customer of DTN for over 10 years!" - Comment from Stuart

"Its working FABULOUSLY for me!! Holy cow...there has been so much I've been missing lately, and with this feed and Linnsoft software...I'm in the game now." - Comment from Chris R.

"You have an excellent product !!!!!!" - Comment from Arely

"Interactive Brokers tick data was inconsistent, so I have switched to using DTN exclusively. It is great to no longer have to worry about my datafeed all day long." - Comment from Philippe

"I've been using Neoticker RT with IQFeed for two months, and I'm very happy with both of the products (I've had IQFeed for two years with very few complaints). The service from both companies is exceptional." - Comment from Public Forum

"I "bracket trade" all major news releases and I have not found one lag or glitch with DTN.IQ feed. I am very comfortable with their feed under all typical news conditions (Fed releases, employment numbers, etc)." - Comment from Public Forum

"The people at Nirvana have very nice things to say about your company and I can see why! Price and service is a potent combination." - Comment from Ed

Home

Recent Posts

Information on DTN's Industries:
DTN Oil & Gas | DTN Trading | DTN Agriculture | DTN Weather

DTN.IQ/IQFeed on Twitter
DTN News and Analysis on Twitter

»Forums Index »Archive (2017 and earlier) »Data and Content Support »SECOND front month contract volumes for Cocoa not matching Bloomberg Volumes

Author	Topic: SECOND front month contract volumes for Cocoa not matching Bloomberg Volumes (4 messages, Page 1 of 1)
sanjayqdt -Interested User- Posts: 2 Joined: Feb 5, 2023 Smithers!	Posted: Feb 5, 2023 01:36 PM Msg. 1 of 4 I pulled the hourly prints for the second front month contract for ICE US Cocoa Futures (CC*2 and, currently, the May 23 expiry) from the getHistory API. I noticed that the volume for daily traded contracts is different from what I see on my Bloomberg terminal. If I sum up the hourly volumes traded, I come to ~12,000 contracts traded on Feb 1 (Wednesday) and if I compare this to Bloomberg, I see ~23,000 contracts traded. I don't understand why these volumes would be different when the prices seem to match?
DTN_mark_e -Interested User- Posts: 49 Joined: Sep 25, 2014	Posted: Feb 6, 2023 07:54 AM Msg. 2 of 4 Hello, we see no issue with the volume value for the hour bars for 2/1 on @CCK23. We show 22719. You can verify this by using the IQFeed Time & Sales app (found in the IQFeed Applications folder on your desktop). Perhaps on your data pull you aren't counting the implied trades. Trading Markets Customer Service 800-779-7299 (DTNIQ & IQFEED) www.dtn.com/trading \| http://www.iqfeed.net
DTN_Gary_Stephen -DTN Guru- Posts: 372 Joined: Jul 3, 2019	Posted: Feb 6, 2023 08:26 AM Msg. 3 of 4 By "getHistory", do you mean the legacy COM objects that start with reqHistory, as described at http://www.iqfeed.net/dev/api/docs/docs52/HistoricalviaCOM.cfm ? Or are you using the modern TCP/IP history requests, like HIT or HID? Sincerely, Gary Stephen DTN IQFeed Implementation Support Specialist
sanjayqdt -Interested User- Posts: 2 Joined: Feb 5, 2023 Smithers!	Posted: Feb 6, 2023 09:14 AM Msg. 4 of 4 getHistory is actually internal code, I apologize, I misunderstood what a colleague's code was doing. I see now that the values match. Thanks for the quick response.