Retrieve a bank operation
GET/api/v1/bank_operations/:id
Returns one bank operation. The path carries no workspace: the id is resolved across every workspace your token holds a grant on, and an operation outside them is indistinguishable from one that does not exist.
projection is the field to read after a statement commit - it says whether the line reached the ledger, and projection.exported whether that entry has since left the books. Both are derived on every read rather than stored.
Request
Responses
- 200
- 401
- 403
- 404
The bank operation.
The request carries no bearer token, or one that is invalid or expired.
Two causes, and they sit on opposite sides of the record lookup. The OAuth SCOPE is checked FIRST, before this operation is resolved at all: a GET needs read, and a write-only or destroy-only token is refused here even for an id that does not exist or that you could not read anyway - so a 403 on a GET is worth ruling out before you go looking for a permissions problem on the record. The other cause is the bank_reconciliation FEATURE being off for the workspace the operation belongs to, and that one IS resolved after reachability: an operation your token cannot read is a 404, never a 403, so this status never confirms that an id exists outside your grants. The example below is refused by the feature.
No operation with this id is reachable by the token's grants. One belonging to another workspace answers the same way, so the response cannot be used to probe for one.