# POST /api/v1/payment-suggestions/bulk-accept

> Bulk accept payment suggestions

- **Tag:** automation-review
- **Operation ID:** `bulk_accept_payment_suggestions`

## Description

Accept many pending invoice (deposit -> invoice) or bill (payment -> bill) match suggestions at once: the `suggestion_ids` you name, or every pending suggestion at or above `min_confidence` (default 0.85), optionally for one customer / vendor (`party_id`) and a bank-transaction date range. Each accept is isolated, so a bad row never loses the rest (`results` lists every one). The batch is one `payment_match` automation run: undo it with `POST /automation-runs/{run_id}/undo`. `dry_run` lists what would be accepted.

## Authentication

Bearer token in `Authorization` header.
Required header: `x-business-id: <business uuid>`.

## Request body

Schema: `BulkAcceptPaymentSuggestionsRequest`

- `kind` (string · required) (one of: invoice, bill) — invoice = deposits matched to invoices, bill = payments to bills
- `suggestion_ids` (array · string) — Accept exactly these suggestions (the filter is then ignored)
- `min_confidence` (number) — Filter: lowest confidence to accept (default 0.85)
- `party_id` (string) — Filter: one customer (invoice) or vendor (bill)
- `start_date` (string · date) — Filter: earliest bank-transaction date
- `end_date` (string · date) — Filter: latest bank-transaction date
- `limit` (integer)
- `dry_run` (boolean) — List what would be accepted; change nothing
- `plan_hash` (string) — plan_hash of the dry run; refused if the suggestions moved since

## Responses

### 200 — Successful Response

Schema: `SuccessEnvelope_BulkAcceptPaymentSuggestionsResponse_`

- `success` (boolean)
- `message` (string)
- `code` (string)
- `data` (BulkAcceptPaymentSuggestionsResponse)

### 400 — Bad Request - Invalid input

Schema: `ErrorResponse`

- `error` (string · required) — Error category: `validation_error`, `unauthorized`, `forbidden`, `not_found`, `conflict`, `rate_limited`, `server_error`, or `service_unavailable`.
- `message` (string · required) — Human-readable explanation, safe to show to end users.
- `code` (string · required) — Stable machine-readable code in `CATEGORY_NNN` form (e.g. `NOT_FOUND_006`, `AUTH_010`, `GEN_002`).
- `request_id` (string) — Correlation id for support requests. Echoes the `x-request-id` request header when one was supplied.
- `errors` (object) — Field-level validation messages keyed by field name. Present on 400/422 validation failures only.

### 401 — Unauthorized - Missing or expired token, an MCP OAuth token used against the REST API, or no access to this business

Schema: `ErrorResponse`

- `error` (string · required) — Error category: `validation_error`, `unauthorized`, `forbidden`, `not_found`, `conflict`, `rate_limited`, `server_error`, or `service_unavailable`.
- `message` (string · required) — Human-readable explanation, safe to show to end users.
- `code` (string · required) — Stable machine-readable code in `CATEGORY_NNN` form (e.g. `NOT_FOUND_006`, `AUTH_010`, `GEN_002`).
- `request_id` (string) — Correlation id for support requests. Echoes the `x-request-id` request header when one was supplied.
- `errors` (object) — Field-level validation messages keyed by field name. Present on 400/422 validation failures only.

### 403 — Forbidden - Insufficient permissions

Schema: `ErrorResponse`

- `error` (string · required) — Error category: `validation_error`, `unauthorized`, `forbidden`, `not_found`, `conflict`, `rate_limited`, `server_error`, or `service_unavailable`.
- `message` (string · required) — Human-readable explanation, safe to show to end users.
- `code` (string · required) — Stable machine-readable code in `CATEGORY_NNN` form (e.g. `NOT_FOUND_006`, `AUTH_010`, `GEN_002`).
- `request_id` (string) — Correlation id for support requests. Echoes the `x-request-id` request header when one was supplied.
- `errors` (object) — Field-level validation messages keyed by field name. Present on 400/422 validation failures only.

### 422 — Validation Error

Schema: `ErrorResponse`

- `error` (string · required) — Error category: `validation_error`, `unauthorized`, `forbidden`, `not_found`, `conflict`, `rate_limited`, `server_error`, or `service_unavailable`.
- `message` (string · required) — Human-readable explanation, safe to show to end users.
- `code` (string · required) — Stable machine-readable code in `CATEGORY_NNN` form (e.g. `NOT_FOUND_006`, `AUTH_010`, `GEN_002`).
- `request_id` (string) — Correlation id for support requests. Echoes the `x-request-id` request header when one was supplied.
- `errors` (object) — Field-level validation messages keyed by field name. Present on 400/422 validation failures only.

## Code samples

### cURL

```bash
curl -X POST 'https://api.ondayzero.com/api/v1/payment-suggestions/bulk-accept' \
  -H 'Authorization: Bearer dz_your_token' \
  -H 'x-business-id: YOUR_BUSINESS_ID' \
  -H 'Content-Type: application/json' \
  -d '{
  "kind": "invoice"
}'
```

### JavaScript

```javascript
const response = await fetch('https://api.ondayzero.com/api/v1/payment-suggestions/bulk-accept', {
  method: 'POST',
  headers: {
    Authorization: 'Bearer dz_your_token',
    'x-business-id': 'YOUR_BUSINESS_ID',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
  "kind": "invoice"
}),
});
const data = await response.json();
```

### Python

```python
import httpx

headers = {
    "Authorization": "Bearer dz_your_token",
    "x-business-id": "YOUR_BUSINESS_ID",
}

payload = {'kind': 'invoice'}

response = httpx.post("https://api.ondayzero.com/api/v1/payment-suggestions/bulk-accept", headers=headers, json=payload)
data = response.json()
```

## See also

- HTML version: https://www.ondayzero.com/docs/reference/automation-review/bulk-accept-payment-suggestions
- OpenAPI slice: https://www.ondayzero.com/docs/reference/automation-review/bulk-accept-payment-suggestions/openapi.json
- Other endpoints in **automation-review**: https://www.ondayzero.com/docs/reference/automation-review (markdown bundle: https://www.ondayzero.com/docs/reference/automation-review.md, OpenAPI: https://www.ondayzero.com/docs/reference/automation-review/openapi.json)
- Endpoint catalog: https://www.ondayzero.com/docs/reference/index.md