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.