Super basic and limited demo of the API call you’ll need to serve the latest KID and KIID
https://finki.io/latestKID.php?isin=IE00BYPLS672
https://finki.io/latestKID.php?isin=IE00BYZK4883
An API key is needed for any fund other than the 2 listed here
The API works with about 19,000 UCITS and just about every tradeable PRIIPs fund across major investment platforms
That is a great API, I just tested it. Is there a document of the ISIN universe it covers? (watched the scrape video). I tried a couple of open-ended (so unlisted) funds, they weren’t there. Obviously closed-end funds can be done by ticker.
Are you referring specifically to the KID and KIID API to auto feed the latest legal documents to client pre-sale to comply with PRIIPS and MiFID rules?
If so, then, it does not appear in the Welcome to FinKi as it took me ages to develop,test and tweak and isn’t something I’m currently willing to give away for free. The other ‘stuff’ generally takes me minutes or hours to compile so I’m not too precious about it. The KID and KIID API call to my mind has some commercial value - especially when you watch the videos and see just how many companies are getting it wrong on a consistent basis. I have further APIs that programmatically extract the key data points from the returned document so you can always have an up to date OCF, performance fee, yield, transaction cost data point. These data points are also wildly off across major platform websites if you look closely. It’s a perfect case of regulations being bought in but not policed or enforced - thereby rendering it useless. No retail client can accurately compare products pre-sale without a lot of googling around. This API solves that. I hope.
psst Finki you should ping @adatherton to invest, it’s one of his areas 
Ha! Love it!
But what this needs is the industry and/or regulator to wake up and realise that compliance with MiFID and PRIIPs rules are on-going and not a one-off “attach this document here and we’re finished”. KID and KIIDs can change on a frequent basis - not just the prescribed “at least annually” in the rule book. An underlying shift in the fund holdings or a wild general market swing and manufacturers (ugh, fund managers, asset managers, ETF providers) are forced to reissue the document. The distribution capabilities of the incumbent data vendors just don’t handle this ad-hoc release of documents very well. Thereby disadvantaging the end consumer – who are the entire reason these annoying things exist in the first place.
I’ll happily take money, but what this needs is a realisation there is a problem and this - at least in part - is a step towards a solution.
Quick and basic demo of the Key Information Document API call and response for any one interested in seeing this thing in action.
https://finki.io/latestKID.php?isin=IE00BYPLS672
https://finki.io/latestKID.php?isin=IE00BYZK4883
This demo is limited to these 2 funds. Any other ISIN will throw an error requesting an API key.
Anyone who wants an API key please message me with your requirements (range of funds you’re interested in and how frequently you’d like to call the API)
These 2 funds in the demo just happen (like magic) to be 2 funds tradeable via Tickr - who are serving an old and inaccurate document!
For a sense of scale and sorry to pick on Tickr, but Tickr currently mis-links ALL funds on their platform. That’s right! I think (although don’t hold me to it) Tickr currently serves their users old and inaccurate KIIDs for EVERY fund tradeable.
That either demonstrates how unpoliced this regulation is OR how little anyone cares!
Hi, I think I’ve come across an issue with ukCurrency. This example looks up Vanguard FTSE All-World UCITS ETF (VWRL), however for some reason the API says that it is USD when it should be GBP/GBX.
https://finki.io/callAPI.php?isin=IE00B3RBWM25&function=ukCurrency
I’ve also noticed it for MSCI China - IE00B44T3H88. Don’t worry if it’s a difficult fix, I can go back to using the Freetrade spreadsheet for currency.
Hi @Gaz92, I think this is because the underlying holding is primarily held in USD. I’m pretty sure VWRL is the UK wrapper for VWRD or VTI, the American etf.
I noticed this “error” myself. But if you Google the ISIN code for the etf it might confirm this. Also if you use the finki uk/sSymbol function I think it will return the USA ticker. I’m not sure what the finki api is doing is necessarily wrong, because the ISIN call is correctly pulling data. It might be worth finki including a note against the function though.
Thanks @Antidev, I just checked the KIID and it is technically USD. No worries then @finki, I’ll just use the Freetrade spreadsheet.
Been offline for a few days. Yep, @Antidev is correct. VWRD is USD, VWRL is GBP. Same ISIN, different Sedol, different Ticker. I’m standardising all the API calls to ISIN for simplicity so in the case of multi currency ETFs this logic is somewhat problematic and can cause a bit of confusion - but better and easy in the other 90% of cases. Either way (barring minimal FX) VWRL and VWRD are the same. About $87 or about £69 with a FX right now of about £1:$1.25
Howdy Finki,
I’ve just been taking a look at the API you’ve set up and I’m hugely impressed, thanks very much for putting this together.
I was playing with the US Dividend History function and have found it’s not sending back valid JSON, it’s missing a comma after the resultcount section, e.g.
[{“resultcount”:“3”}{“dividend”:“1”,“exdate”:“2019-08-14”,“paydate”:“2019-09-12”,“amount”:0.46},{“dividend”:“2”,“exdate”:“2019-05-15”,“paydate”:“2019-06-13”,“amount”:0.46},{“dividend”:“3”,“exdate”:“2019-02-20”,“paydate”:“2019-03-14”,“amount”:0.46}]
I’m assuming it should? Also (hope I’m not pushing my luck here) but is it intended that the content type will always be html/text?
Anyway, thanks again for putting this together, you’re a fast working genius.
Not sure how I’ve previously missed this but @finki, you’re a legend.
Thanks so much for pulling this all together. I’ll admit that I’m new to Sheets (and not great at spreadsheets generally), but this has inspired me to improve my skills so that I can properly track my portfolio.
I’d previously played around with GoogleFinance commands, but that obviously didn’t include ETF tracking, so was looking at having to do things manually. This changes everything 
Off grid right now but will fix this for you tomorrow
You’re clearly beyond novice level so I suspect you’ve used a work around already if you’re spotting content types!
Back in civilisation tomorrow and will sort it.
Thanks for using it. Any suggestions let me know. Any additional data points let me know.
Enjoy
It was my own annoyance at the lack of ETF data that led me to do this!
It was also the high price of big data vendor fees and complexity for novice users that led me to push this project out!
Finki works nicely in excel too if you’re more familiar. If you’d like a simple excel add in to consume this data let me know and I’ll message you over some simple code if you’re at all familiar with the VBA IDE.
Hope you enjoy! Any requirements just message me!
Fixed. Thanks for the heads-up
Looks like I went a bit crazy on the US version - the UK version was fine.
Ok, so a quick question here.
I’ve opened up my ISA this year and have bought into a total of 5 ETFs (while I wait to transfer my current ISA across).They were purchased as ‘basic trades’, and looking at timestamps in the app, everything went through just after 4pm this evening.
My issue is that, when calling the ASK function, 3 of those ETFs have risen in value by an average of 20% each in the 25 mins that followed the purchase and before trading closed.
I guess I’m wondering whether I’m a trading genius or whether I should just be taking the data sources included in the API with a pinch of salt.
Have you checked the prices of those ETFs on Google? Then compared them?
I hadn’t, but I have now.
Yes, it does seem that the ASK prices from the API are inflated somewhat. Guess I’ll go back to the day job.
Finki, happy to provide further info if it would help at all.
@MortimerJazz, Did you use the ukCurrency function along with ukAsk? A lot of the ETFs have a base currency of USD. You might need to convert it back to GBP.
Yes, fine - that’s nailed it.
Thank you - have a heart!