# PUT /api/v1/meta-ads/billing-statements/{statement_id}

> Edit a draft Meta supplier statement

- **Tag:** meta-ads
- **Operation ID:** `meta_ads_update_billing_statement`

## Description

Edit evidence before confirmation. Reopen a confirmed statement first; confirmed allocations cannot silently change.

## Authentication

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

## Parameters

- `statement_id` (path, string · uuid, required)

## Request body

Schema: `MetaAdsBillingStatementRequest`

- `ad_account_id` (string · uuid · required)
- `reference` (string · required)
- `evidence_reference` (string · required) — Supplier invoice/statement reference or document link; manually reviewed, never fetched
- `period_start` (string · date · required)
- `period_end` (string · date · required)
- `currency` (string · required)
- `spend_minor` (integer · required)
- `tax_minor` (integer)
- `credits_minor` (integer)
- `opening_payable_minor` (integer · required)
- `closing_payable_minor` (integer · required)
- `charge_allocations` (object)

## Responses

### 200 — Successful Response

Schema: `SuccessEnvelope_MetaAdsBillingStatementOut_`

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

### 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.

### 404 — Not Found - Resource does not exist

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.

### 409 — Conflict - Resource already exists or is in an incompatible state

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 PUT 'https://api.ondayzero.com/api/v1/meta-ads/billing-statements/{statement_id}' \
  -H 'Authorization: Bearer dz_your_token' \
  -H 'x-business-id: YOUR_BUSINESS_ID' \
  -H 'Content-Type: application/json' \
  -d '{
  "ad_account_id": "00000000-0000-0000-0000-000000000000",
  "reference": "string",
  "evidence_reference": "string",
  "period_start": "2026-01-01",
  "period_end": "2026-01-01",
  "currency": "string",
  "spend_minor": 0,
  "opening_payable_minor": 0,
  "closing_payable_minor": 0
}'
```

### JavaScript

```javascript
const response = await fetch('https://api.ondayzero.com/api/v1/meta-ads/billing-statements/{statement_id}', {
  method: 'PUT',
  headers: {
    Authorization: 'Bearer dz_your_token',
    'x-business-id': 'YOUR_BUSINESS_ID',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
  "ad_account_id": "00000000-0000-0000-0000-000000000000",
  "reference": "string",
  "evidence_reference": "string",
  "period_start": "2026-01-01",
  "period_end": "2026-01-01",
  "currency": "string",
  "spend_minor": 0,
  "opening_payable_minor": 0,
  "closing_payable_minor": 0
}),
});
const data = await response.json();
```

### Python

```python
import httpx

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

payload = {'ad_account_id': '00000000-0000-0000-0000-000000000000',
 'reference': 'string',
 'evidence_reference': 'string',
 'period_start': '2026-01-01',
 'period_end': '2026-01-01',
 'currency': 'string',
 'spend_minor': 0,
 'opening_payable_minor': 0,
 'closing_payable_minor': 0}

response = httpx.put("https://api.ondayzero.com/api/v1/meta-ads/billing-statements/{statement_id}", headers=headers, json=payload)
data = response.json()
```

## See also

- HTML version: https://www.ondayzero.com/docs/reference/meta-ads/meta-ads-update-billing-statement
- OpenAPI slice: https://www.ondayzero.com/docs/reference/meta-ads/meta-ads-update-billing-statement/openapi.json
- Other endpoints in **meta-ads**: https://www.ondayzero.com/docs/reference/meta-ads (markdown bundle: https://www.ondayzero.com/docs/reference/meta-ads.md, OpenAPI: https://www.ondayzero.com/docs/reference/meta-ads/openapi.json)
- Endpoint catalog: https://www.ondayzero.com/docs/reference/index.md