I used to be the VP of Engineering at Simple. We always wanted to release an API but weren't able to. They're working on a bunch of great stuff over there, but I hope they do release one someday.

As someone who uses Simple every day, I'd kill for an API. Would be cool to do some analytics on my spending on top of what they already provide.

Why weren't they able to? Lack of time, demand, security, did it wrong and had to start over?

I can no longer speak for them, but while I was there we were entirely focused on getting our core consumer online banking product right. We did not want to launch an API without properly supporting the community, and we didn't want to distract ourselves from executing on the core product. There were other complexities but it's not appropriate for me to say any more.

there are api endpoints, just not documented, right?

check devtools when logged into simple.

These libraries are screen scrapers with no security control. You can't make a read only version that prevents an attacker from using your API key to steal your money, for example.

I want to completely disclose Neocities financing, and lack of API for safely doing this has been a frustrating problem.

You would have to proxy the requests on your server, enforce read-only on your public facing API, and keep the token sever-side for talking to the bank?

Put varnish in front of your API to act as a caching layer and prevent anyone from causing your server to overload the bank API.