And in the sense of true customer service, did they not include an overview of the changes. Yahoo only included a link to the webpage where the T&C's can be found.
True, but the bottom line is that they were giving the data for free without any advertising to support it. Why do it? What do they gain by hosting data for nothing? I wish they would give away the data for free, but it can't be expected.
I agree with what you are saying but lets say you were an end user of the yahoo finance website and follow their expected typical use cases. Simply viewing the site with your browser is now extremely slow. They are screwing things up even among their intended end users.
Not surprised... http://slopeofhope.com/2017/05/two-blondes-two-fates.html It's a company that had a ton of potential in the 90s, but its management did not live up to the optimism. Not sure why Verizon bought them. Pulling EOD historical data was the only thing I used Yahoo for. I use Finviz whenever I want to pull up a quick chart.
There seems to be a general crackdown on financial data scraping. It used to possible to scrape free historical currency data from oanda until just recently.
I never understood why financial exchanges want to tightly regulate their real-time data distribution and historical data redistribution...is it nothing more than they just want to make more money on selling the data?
Has anyone posted this? Yahoo officially killed the historical api. https://forums.yahoo.net/t5/Yahoo-Finance-help/ichart-stopped-working-2-days-ago/m-p/251679#M3154
i was referring to limitation on historical data requests,not requests for real time data ------------ Pacing Violations All of the API technologies support historical data requests. However, requesting the same historical data in a short period of time can cause extra load on the backend and subsequently cause pacing violations. The error code and message that indicates a pacing violation is: 162 - Historical Market Data Service error message: Historical data request pacing violation The following conditions can cause a pacing violation: Making identical historical data requests within 15 seconds; Making six or more historical data requests for the same Contract, Exchange and Tick Type within two seconds. https://www.interactivebrokers.com/en/software/api/api.htm