Yahoo Broke (1 Viewer)

[Privateer]

I have an Access database that goes to http://download.finance.yahoo.com/ and gets me about a dozen numbers/dates for each stock ticker I send it. And I loop through about fifty companies. Been working for over a year, really got to rely on it. Now on Monday, the code failed. The page cannot be located. Does anyone out there download stock information, for free of course, from another site? I could really use that URL. I suspect the new boss at Yahoo, after canceling their work from home policy, is now tightening up on the freebies. And I don't need up to the second data, twenty minutes old is fine, I just don't want to type all that in manually. Thanks in advance.

 

[plog]

It seems Yahoo does have an API for getting stock data, however, the only documentation I could find was from Google Code: https://code.google.com/p/yahoo-finance-managed/wiki/csvQuotesDownload

 

[Privateer]

Thanks plog, but your google site tells me to use the URL that I now know to be broken, so not much help there. Does anyone know of another site that allows free market downloads?

 

[plog]

This url actually does work:

http://download.finance.yahoo.com/d/quotes.csv?s=%40%5EDJI,GOOG&f=nsl1op

Perhaps the f parameter of your querystring is no longer valid?

 

[Privateer]

My apologies, your link does work, but the change was not in the f string. By getting the properties of your link I was able to figure it out. Thanks for the follow up despite my rude reply. Below is what I had when I was looking up General Electric:

URL: http://download.finance.yahoo.com/d/quotes.csv/q?s=GE&f=xsnpod1l1dqr1jk&ignore=.csv

and what ended up working:
URL: http://download.finance.yahoo.com/d/quotes.csv?s=@^DJI,GE&f=xsnpod1l1dqr1jk&e=.csv

I took out the /q after the csv and changed &ignore to &e. I also added in the special characters string %40%5EDJI, just before the ticker symbol as your link suggested. I went through each letter of the f string and there were no changes there, but it was a good place to look. So I thank you again for the follow up.