# POST /api/v1/headcount-plans/{plan_id}/positions

> Add position

- **Tag:** headcount
- **Operation ID:** `add_planned_position`

## Description

Add a position to a headcount plan.

## Authentication

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

## Parameters

- `plan_id` (path, string, required)

## Request body

Schema: `PlannedPositionCreateRequest`

- `title` (string · required) — Job title.
- `department` (string) — Department.
- `annual_salary_cents` (integer · required) — Annual base salary in cents.
- `benefits_multiplier` (integer) — Fully loaded cost as a percent of salary: 130 = salary plus 30% for benefits and employer taxes.
- `start_date` (string · date · required) — First day in the role.
- `end_date` (string · date) — Last day in the role; empty for open-ended.
- `status` (PositionStatusEnum) → `PositionStatusEnum` — planned, approved, filled or cancelled (cancelled is left out of every total).
- `notes` (string) — Notes.
- `ledger_id` (string) — Expense account the cost lands in when the plan is pushed to a budget.
- `employee_id` (string) — People roster row that fills the position.

## Example request

```json
{
  "annual_salary_cents": 18000000,
  "benefits_multiplier": 125,
  "department": "Engineering",
  "start_date": "2027-03-01",
  "title": "Senior Engineer"
}
```

## Responses

### 201 — Successful Response

Schema: `SuccessEnvelope_PlannedPositionResponse_`

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

### 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 POST 'https://api.ondayzero.com/api/v1/headcount-plans/{plan_id}/positions' \
  -H 'Authorization: Bearer dz_your_token' \
  -H 'x-business-id: YOUR_BUSINESS_ID' \
  -H 'Content-Type: application/json' \
  -d '{
  "annual_salary_cents": 18000000,
  "benefits_multiplier": 125,
  "department": "Engineering",
  "start_date": "2027-03-01",
  "title": "Senior Engineer"
}'
```

### JavaScript

```javascript
const response = await fetch('https://api.ondayzero.com/api/v1/headcount-plans/{plan_id}/positions', {
  method: 'POST',
  headers: {
    Authorization: 'Bearer dz_your_token',
    'x-business-id': 'YOUR_BUSINESS_ID',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
  "annual_salary_cents": 18000000,
  "benefits_multiplier": 125,
  "department": "Engineering",
  "start_date": "2027-03-01",
  "title": "Senior Engineer"
}),
});
const data = await response.json();
```

### Python

```python
import httpx

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

payload = {'annual_salary_cents': 18000000,
 'benefits_multiplier': 125,
 'department': 'Engineering',
 'start_date': '2027-03-01',
 'title': 'Senior Engineer'}

response = httpx.post("https://api.ondayzero.com/api/v1/headcount-plans/{plan_id}/positions", headers=headers, json=payload)
data = response.json()
```

## See also

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