Record Mercury Bank Transaction As Vendor Deposit
POST/api/mercury/bank-transactions/:transaction/record-deposit
Records an outgoing transfer as a paid vendor deposit on a purchase order — e.g. a deposit or pre-shipment balance wired straight from Mercury. An open deposit on the order for exactly this amount is paid; otherwise a new deposit is created for the order's supplier, approved and paid, dated on the bank date. When a vendor deposit approval policy needs someone else's approval, the deposit is created and waits, the transaction stays open with the new deposit suggested, and message says who it waits on.
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.
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.