Approve Mercury Payment Request
POST/api/mercury/payment-requests/:request/approve
For connections that approve payments in SKU.io: approves a request that is awaiting approval in SKU.io and sends it straight from Mercury.
This endpoint currently requires session authentication; Personal Access Token scope support is in progress.
Anyone with the permission can approve it, including the user who created the payment. If Mercury refuses the payment, the request goes back to awaiting approval and the 422 carries Mercury's message.
Authentication: Requires Bearer token and the Approve Mercury payments permission (mercury.approve, granted per role; admins always have it). Without it the request returns 403.
Under an enabled bill payment approval policy, the purchase invoices it pays must still be approved for these amounts when it is approved here; otherwise 422 with code approval_required.
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 Content
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.