# PUT /api/v1/posting-defaults

> Update invoice posting defaults

- **Tag:** posting-defaults
- **Operation ID:** `update_posting_defaults`

## Description

Set the ledger for any of the four invoice posting roles, or send null to go back to the system ledger. Omitted roles are unchanged. Inactive ledgers and ledgers of the wrong account type are refused. Only new postings use the change; entries already posted stay.

## Authentication

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

## Request body

Schema: `PostingDefaultsUpdate`

- `invoice_sales_ledger_id` (string) — Revenue ledger credited by invoices
- `invoice_cogs_ledger_id` (string) — Expense ledger debited for cost of goods sold
- `invoice_inventory_ledger_id` (string) — Asset ledger credited when inventory is relieved
- `invoice_ar_ledger_id` (string) — Asset ledger debited for the receivable

## Responses

### 200 — Successful Response

Schema: `SuccessEnvelope_PostingDefaultsResponse_`

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

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

### 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/posting-defaults' \
  -H 'Authorization: Bearer dz_your_token' \
  -H 'x-business-id: YOUR_BUSINESS_ID' \
  -H 'Content-Type: application/json' \
  -d '{
  "invoice_sales_ledger_id": "string",
  "invoice_cogs_ledger_id": "string",
  "invoice_inventory_ledger_id": "string",
  "invoice_ar_ledger_id": "string"
}'
```

### JavaScript

```javascript
const response = await fetch('https://api.ondayzero.com/api/v1/posting-defaults', {
  method: 'PUT',
  headers: {
    Authorization: 'Bearer dz_your_token',
    'x-business-id': 'YOUR_BUSINESS_ID',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
  "invoice_sales_ledger_id": "string",
  "invoice_cogs_ledger_id": "string",
  "invoice_inventory_ledger_id": "string",
  "invoice_ar_ledger_id": "string"
}),
});
const data = await response.json();
```

### Python

```python
import httpx

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

payload = {'invoice_sales_ledger_id': 'string',
 'invoice_cogs_ledger_id': 'string',
 'invoice_inventory_ledger_id': 'string',
 'invoice_ar_ledger_id': 'string'}

response = httpx.put("https://api.ondayzero.com/api/v1/posting-defaults", headers=headers, json=payload)
data = response.json()
```

## See also

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