# POST /api/v1/invoices/drafts/bulk-delete

> Bulk delete draft invoices

- **Tag:** invoices
- **Operation ID:** `bulk_delete_draft_invoices`

## Description

Delete many draft invoices in one call: name them with `invoice_ids`, or set `all_drafts` (optionally with a due-date window) to clear every draft. Only drafts can be deleted: a selection that includes any other status is refused whole (400) and nothing is deleted. Each deletion runs the single-invoice path in its own savepoint, so a draft that cannot be deleted is reported without blocking the rest.

## Authentication

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

## Request body

Schema: `BulkDeleteDraftInvoicesRequest`

- `invoice_ids` (array · string) — Draft invoice UUIDs to delete (1-500). Every id must be a draft or nothing is deleted. Mutually exclusive with all_drafts.
- `all_drafts` (boolean) — Delete every draft invoice of the business, optionally limited by start_date / end_date. Mutually exclusive with invoice_ids. At most 500 are deleted per call; `remaining` says how many are left.
- `start_date` (string · date) — With all_drafts: only drafts due on or after this date.
- `end_date` (string · date) — With all_drafts: only drafts due on or before this date.
- `dry_run` (boolean) — List the drafts that would be deleted; delete nothing.

## Responses

### 200 — Successful Response

Schema: `SuccessEnvelope_BulkDeleteDraftInvoicesResponse_`

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

### 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/invoices/drafts/bulk-delete' \
  -H 'Authorization: Bearer dz_your_token' \
  -H 'x-business-id: YOUR_BUSINESS_ID' \
  -H 'Content-Type: application/json' \
  -d '{
  "invoice_ids": [],
  "all_drafts": false,
  "start_date": "2026-01-01",
  "end_date": "2026-01-01",
  "dry_run": false
}'
```

### JavaScript

```javascript
const response = await fetch('https://api.ondayzero.com/api/v1/invoices/drafts/bulk-delete', {
  method: 'POST',
  headers: {
    Authorization: 'Bearer dz_your_token',
    'x-business-id': 'YOUR_BUSINESS_ID',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
  "invoice_ids": [],
  "all_drafts": false,
  "start_date": "2026-01-01",
  "end_date": "2026-01-01",
  "dry_run": false
}),
});
const data = await response.json();
```

### Python

```python
import httpx

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

payload = {'invoice_ids': [],
 'all_drafts': False,
 'start_date': '2026-01-01',
 'end_date': '2026-01-01',
 'dry_run': False}

response = httpx.post("https://api.ondayzero.com/api/v1/invoices/drafts/bulk-delete", headers=headers, json=payload)
data = response.json()
```

## See also

- HTML version: https://www.ondayzero.com/docs/reference/invoices/bulk-delete-draft-invoices
- OpenAPI slice: https://www.ondayzero.com/docs/reference/invoices/bulk-delete-draft-invoices/openapi.json
- Other endpoints in **invoices**: https://www.ondayzero.com/docs/reference/invoices (markdown bundle: https://www.ondayzero.com/docs/reference/invoices.md, OpenAPI: https://www.ondayzero.com/docs/reference/invoices/openapi.json)
- Endpoint catalog: https://www.ondayzero.com/docs/reference/index.md