---
updatedAt: 2026-09-30T17:50:34.235Z
---

Fetch the complete documentation index at: https://docs.avvio.xyz/llms.txt. Use this file to discover all available pages before exploring further. Append .md to any documentation page URL to get its markdown version.

# Confirm a payout batch

`POST https://api.avvio.xyz/business/api/v1/payments/organizations/{orgId}/payouts/batches/{batchId}/confirm`

Proceed with the valid lines of a held run.

Only legal while the batch is `awaiting_confirmation`. The valid lines
go to creation; `invalid` lines stay refused. Correct them and resubmit as a new batch. Confirming a batch that already moved on
answers `409 PAYOUT_BATCH_NOT_CONFIRMABLE` naming where it actually is.

**When your organization requires approval on API payouts**, the run
is held at `awaiting_confirmation` whatever `autoCommit` said, and the
first confirm answers **202** with one approval for the whole run, never one per line. A repeat confirm returns the same approval; once
your approvers reach quorum the run is released within a minute. If an
approver rejected it, confirm answers `409 PAYOUT_BATCH_AWAITING_APPROVAL`.

## Parameters

- `orgId` (path, required) — The opaque organization id issued to you, normally CUID-shaped (for example `cmsx…`). It is not an `org_`-prefixed alias. Pass it unchanged in every organization-scoped path.
- `batchId` (path, required) — From the 202 that accepted the run, or the batch list.
- `Idempotency-Key` (header, required) — A unique value per logical operation, 1-255 chars of `A-Z a-z 0-9 _ . : -`. Reuse it to retry. Same key with the same body replays the stored response; same key with a *different* body is a `409`, because answering with the first call's result would hand you a receipt for a payout you did not request. A `4xx` releases the key, so you can fix the body and reuse it. **Reuse it; do not generate one per attempt.** A key minted per attempt defeats replay entirely: every retry looks like a new request, so every retry pays. We also watch for an identical body arriving under a *different* key within 15 minutes and refuse it with `DUPLICATE_REQUEST_DETECTED`. Records are kept for 7 days. That is a retention window only: there is no path where an expired key is re-executed.

## Example

```bash
IDEMPOTENCY_KEY=$(uuidgen)  # new key per call; reuse it only to retry this exact request
curl -s -X POST "$AVVIO_BASE_URL/payments/organizations/$AVVIO_ORG_ID/payouts/batches/$batchId/confirm" \
  -H "x-api-key: $AVVIO_API_KEY" \
  -H "Idempotency-Key: $IDEMPOTENCY_KEY"
```

## Responses

- `200` — The batch, now `creating`.
- `202` — Held for your approvers. One approval covers the run; nothing is created until it is approved.
- `400` — Missing (`IDEMPOTENCY_KEY_REQUIRED`) or malformed (`IDEMPOTENCY_KEY_INVALID`) `Idempotency-Key`.
- `401` — The key was refused. Nothing ran. - `UNAUTHORIZED`: missing, invalid or revoked, or a key on a route that does not accept one. - `KEY_EXPIRED`: the key passed the expiry it was issued with. Issue a new one; an expired key cannot be rotated. - `KEY_IP_NOT_ALLOWED`: the key is pinned to source addresses and this request came from another.
- `403` — A valid key that may not make this write. Nothing was changed. - `MASS_PAYOUTS_DISABLED`: batch submission is off for your organization. `GET /policy` lists `mass_payouts` in `features` when it is on; contact support to enable it. - `FORBIDDEN`, `ACCOUNT_BLOCKED`, `LIVE_KEY_ORG_NOT_APPROVED`, `INSUFFICIENT_SCOPE`: as on every write (`ForbiddenWrite`).
- `404` — `BATCH_NOT_FOUND`: no such batch in this organization.
- `409` — `PAYOUT_BATCH_NOT_CONFIRMABLE`: the batch is not awaiting confirmation. `PAYOUT_BATCH_AWAITING_APPROVAL`: an approver rejected the run; the approval id is in `detail` (there is no `approvalId` field). Or an idempotency conflict (`IDEMPOTENCY_KEY_CONFLICT`, `IDEMPOTENCY_KEY_REQUEST_IN_PROGRESS`).
- `429` — Too many requests. The default ceiling is **100 requests per minute per API credential** on a 60-second window. High-volume payout and reconciliation routes declare a 600/minute override, and batch submission a 30/minute ceiling. A separate 2,000/minute per-source-IP abuse ceiling always applies. Obey `Retry-After`; it is in seconds and is authoritative. A 429 means the request was refused before the handler ran. Retry reads normally; retry an idempotent mutation with its same `Idempotency-Key`.

Machine contract: [partner-payouts.openapi.yaml](/partner-payouts.openapi.yaml), operation `confirmPayoutBatch`.