Confirm Mercury Bank Transaction Match
POST/api/mercury/bank-transactions/:transaction/confirm
Confirms one of the transaction's suggestions. A suggestion of kind payment links the payment already recorded in SKU.io; a suggestion of kind payable records the transfer against that bill, purchase invoice or vendor deposit, dated on the bank date (a vendor deposit is marked paid on that date, so it appears in the purchase order's cash flow there).
accounting:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Requires Bearer token and the Record bank transactions permission (mercury.record). It records money that has already moved, so it never needs the Pay with Mercury permission (mercury.pay); roles and users that held mercury.pay when mercury.record was introduced were given it automatically.
Returns 422 when the suggestion is gone, the payment is already matched to another transaction, or the transaction is already matched or ignored.
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Unprocessable Entity
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.