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)

"Can I get another account from you? I am tired of ******* going down so often" - Comment from George

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

"I noticed that ******* quotes locked up shortly after the interest rate announcement yesterday while yours stayed stable." - Comment from Ron in Utah

"This beats the pants off CQG, I am definitely switching to the ProphetX 3.0!" - Comment from Stephen

"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

"As a past ******* customer(and not a happy one), IQ Feed by DTN is a much better and cheaper product with great customer support. I have had no problems at all since switching over." - Comment from Public Forum

"IQ feed is brilliant. The support is mind-bending. What service!" - Comment from Public Forum Post

"I had always used ******* but for the past 2 weeks have been trying DTN IQFeed. Customer support has been extraordinary. They call just to make sure your problem hasn't recurred." - Comment from Public Forum

"I've been using IQFeed 4 in a multi-threaded situation for the last week or two on 2600 symbols or so with 100 simultaneous daily charts, and I have had 100% responsiveness." - Comment from Scott

"I started a trial a few weeks back before the market went wild. DTN.IQ didn’t miss anything and beat my other provider. I decided to stay with you because of the great service through all the volatility." - Comment from Mike

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: 394 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.