Despite a software background, I already have wasted two hours trying to untangle the API / Token / Bank Feed mess. The protocol is obscure, documentation non-existent and nothing works. There is no useful error reporting that might lead to a solution - other than to abandon my second chance trying Manager.
Dear @atd,
I’m sorry to hear that but I don’t see the mess you are referring to. The bank feed provider settings has only two fields, one of them is a name:
The api2 is following OpenApi shcema with everything you need to know about paths, methods, parameters, and fields is listed in .json format on this url: https://{ your domain }/api2.
My advise is to contact your bank feed provider so that they can give you a working endpoint and for the api, please hire someone with experience working with OpenApi schemas.
Your own reply is illustrative of the chaos. "Endpoint” shows no indication as to what on earth it wants. Having got through this, authorisation tokens etc., the fee continues to be rejected without a description as to why. It’s supposed to be accounting, not system programming and the suggestion to hire someone just to make it work is ridiculous.
On another system, it took just a minute to establish a working feed. That’s how it could and should be.
Error connecting to http://127.0.0.1:57070/api2/.well-known/openid-configuration. No connection could be made because the target machine actively refused it. (127.0.0.1:57070).
If it’s not a poor implementation as I suggest, then you will no doubt be able to tell me from that error message, how to fix it!
Endpoint means url of your bank feed provider.
Unlike other accounting software who have a set list of bank feed providers – who are affiliates more likely than not, Manager does not affiliate itself with any of them, instead it just gives the user the open option to connect to any provider they like without forcing the users to a set list.
To do that, you just need to have the providers endpoint (url) and feed it into the related field.
It appears that you have fed Manager its own address.
Instead, ask your bank feed provider for their endpoint.
No, the bank does not provide the endpoint and if it did, it would have been a small matter to include that direction next to the input control.
@atd implementation is based on FDX standard - https://financialdataexchange.org/
Speficially, I’ve implemented subset defined by Plaid.com from here: https://plaid.com/core-exchange/docs/
But it does seem like standard is dead as far as worldwide adoption goes. I’m planning to remove Bank Feed Providers feature and bank feeds will be facilitated by Manager extensions which is more flexible and simpler approach.
Thank you for the explanation lubos. I struggled for many hours with this.
Looking at the Guide documentation, I agree there is considerable scope for improvement https://www.manager.io/guides/bank-and-cash-accounts
Indeed. I wish I had started writing an accounting system myself, a couple of months ago. I had no idea how the market had developed, particularly in the direction of online implementations, with relatively few exceptions.