Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
I am looking for a website/webservice from where I could programmatically get the information about current (possibly past?) interest rates to calculate Rollover Interest/Carry Trade fees.
I would rather avoid web scraping if possible so a webservice with nice API would be the best.
Any suggestions?
Can you help answer these questions from other members on NexusFi?
I haven't checked Quandl for that as I was looking for something kept more up to date (that would inform me if the interest rate changed). Quandl may be good for the past interest part though, although I can't verify this since my free trial expired and this seems to be Premium Data: https://www.quandl.com/c/economics/interest-rate-sge-by-country
Can someone with premium access verify if the above includes historical interest rates data?
Quandl I'm sure is updated regularly but the pricing is just laughable IMO.
If you are not using the quandl API I would think your only real option for free interest rate data would be to scrape the wall street journal site. Bloomberg obviously would be able to do this but I don't drive a Ferrari.
I'm not sure it's very useful to have different databases, different tables are enough IMHO.
The good question is more: what would be the tables structure.
On my side I'm working on something similar with a single database and a table per bar type (tick/minute/day). I'm not sure it's the best option on performance point of view, as the tick table is going to be very very large, but on a "logical" point of view I don't like the idea of having a distinct table per symbol.
True for many datasets on Quandl. On the left side there is a section "validate" with a link to the dataset source. Many times the source may have their own API you can tap directly or scrape the page if no API is provided. That way you can update on your terms. I think the value of Quandl is that they provide a single source for normalized datasets and their API is really easy to use, so you can save a lot of time testing ideas out.