APIs for accessing user portfolio etc


To provide a bit of background: one of my consistent frustrations with brokers in UK is that you don’t have easy access to your portfolio data via API unless you are logged in and/or using a blessed application of some sort.

This seems to be a trend that’s reversing in banking (with open API initiatives finally happening). The lack of the openness just resulted in people using web-scrapers or other mechanisms that involved providing credentials - this is obviously insecure and unsatisfactory.

Hence, it would be very interesting to have a well-documented API to enable read-only access to a limited subset of a user’s portfolio functionality.

Auth could be done securely via OAuth2 (or similar), allowing a much more controllable and secure experience. For example, you can tie the token and/or credentials to a specific account and app, with easy revocation and carefully scoped permissions.

I’d recommend OpenAPI 3.x (fka Swagger) for documentation, as this is handy for generation of docs and stubs, amongst other things.

Use-cases would include:

  • Allowing smooth and secure integration into new and existing financial applications.
  • Displaying current portfolio value, stock allocations, etc, without needing to log in or re-export data after every trade.
  • Allows safe and simple scripting for software nerds like me ;-).

Just writing this makes me wonder what interesting things you could do with Elasticsearch and Kibana, hmm.

I realise this would likely not be the highest priority, but thought I’d put it out there. There’s a heck of a lot of additional value to a platform when there is openness and integration opportunities.


Public API
IFTTT Integration
Feature Requests (Open Wiki) :bulb:
(Viktor) #2


API is on the list of ideas to work on. It’s still further out though.

One of the big goals of the upcoming Crowdcube round is to shore up engineering. We’re planning to hire 5 engineers, which will almost double our team size.

Benjamin Graham‘s 10 rules of value investing 🤔

Would be a fantastic thing to get going early on; would allow the community to get involved even further from an early stage and dream up even more use-cases.
Think I read you guys were doing early pentesting of the platform? Something like this would be an obvious target for inclusion in that if it isn’t already :slight_smile:


Sounds great. API-related stuff is what I’ve worked on for the last few years (I work in open source). I’m happy to contribute to the discussions when the topic comes around for more detailed technical exploration.

I have in mind a few excellent open source projects that would work well with the stack you’ve published, depending how you approach things.


For us and external parties like EMMA app ( @edoardomoreni )

The other plus side of this is, we can match it up to Zapier ourselves as they have a API source.

(Pablo) #6

Dear team,

Are you planning to release an API sometime in the near future as soon as the app is fully available to everyone?

For now and as you start adding more tickers, it would be very useful if you could provide a JSON/XML resource with the list of the current investable universe as well as the exchange associated to it. This will do for now :slight_smile:

Thanks again!

(Alex Sherwood) #7

We’d definitely like to provide an API at some point (I’m a big fan of the idea :smile:) but this isn’t on our roadmap for the next 12 months.

(Pablo) #8

Thanks! Whenever you have a bit more time (low priority jira!), it would be good if you could at least produce a version of the FT stock universe spreadsheet that contains all the current tradable symbols that is from time to time synchronised to the actual tradable universe. The current one on google docs has quite a few hidden rows and has symbols that are unavailable (eg FERG), and is difficult to read with a script when I produce a quant portfolio allocation.