Hi,
I’m building a private integration against my own account using a personal
bearer token (REST API v2 beta).
Looking at the Swagger spec, /bank_accounts/{id}/transactions only exposes
GET (query) and POST (create *untagged*). I can’t find a PUT/PATCH or any
tag endpoint, so as far as I can tell an existing untagged bank transaction
can’t be tagged over the API.
Two questions:
1. Is that right, or is there a supported route I’ve missed - allocating an
untagged transaction to an invoice/purchase, a nominal, or a transfer
between two bank accounts?
2. If not, is the intended pattern to let the API create the bank entry
itself - i.e. POST /client_payments (or /purchases with an embedded
payment) with nominal_code set - and to keep the Open Banking feed
switched off so the two don’t produce duplicates? I’d rather follow the
intended design than work around it.
Related: is there any way to delete or reverse a bank transaction created
in error via POST, or does that have to be done in the UI?
If tagging genuinely isn’t available, please treat this as a feature
request - an endpoint to tag an existing transaction (to an invoice,
nominal or transfer) would make bank automation via the API a lot more
practical.
Thanks!