# Create a position

Operation ID: `createPosition`

Group: People Management › Positions

[Open in the interactive reference](https://docs.api.lensing.ai/lensing/v1/endpoints/createPosition)

`POST /people/positions`

Retry-safe: A write that accepts Idempotency-Key: repeating a request with the same key replays the stored answer instead of executing twice.

Creates a position. A position's name must be unique among positions with the same job profile. If you leave out jobProfileId, any position with the same name counts as a duplicate, and the request fails with DUPLICATE_POSITION.

The response contains only the new position's id. Read the full record with GET people/positions/:id.

## Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `Api-Version` | header | string · v1 | yes | The API version this request targets, named by its public identifier. Required on every request; omitting it, or naming a version this company does not have, is answered with 400. This document describes version `v1`. |
| `Idempotency-Key` | header | string | no | An opaque caller-chosen string (1-255 characters) that makes this request safe to retry. Repeating the same key with an identical request body replays the original response instead of re-executing - but only once that original request succeeded; a failed attempt re-executes on retry. Repeating the key with a different body is answered with 422. A key still in flight is answered with 409 - as is a key whose original request was interrupted before it finished, for a few minutes afterwards, until that attempt is presumed dead. A completed response stays replayable for 24 hours. The key is scoped to the caller, not to the action: reusing it for a different action is answered with 409 or 422 rather than treated independently. On read actions this header is ignored. On write actions that cannot offer the guarantee it is answered with `400 IDEMPOTENCY_NOT_SUPPORTED` rather than silently ignored. |

## Request body

Required, `application/json`: createPositionInput.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `name` | string | yes | The display name of the position. |
| `description` | string | no | A free-form description of the position's responsibilities. |
| `desiredHeadcount` | number | no | The target number of people to fill this position. |
| `expectedSalary` | number | no | The expected annual salary for this position, in the entity's currency. |
| `startDate` | string | no | The date the position becomes active. Use format YYYY-MM-DD. |
| `endDate` | string | no | The date the position becomes inactive. Use format YYYY-MM-DD. Omit for an open-ended position. |
| `overtimeStatus` | any | no | The overtime eligibility of the position. One of: `"EXEMPT"`, `"NON_EXEMPT"`. |
| `hiringManagerId` | string | no | The identifier of the employee who is the hiring manager. See id on GET people/person/:id. |
| `jobProfileId` | string | no | The identifier of the job profile the position is associated with. There is no endpoint for it. |
| `regionId` | string | no | The identifier of the region the position is based in. There is no endpoint for it. |

```json
{
  "name": "<name>",
  "description": "<description>",
  "desiredHeadcount": 0,
  "expectedSalary": 0,
  "startDate": "<startDate>",
  "endDate": "<endDate>",
  "overtimeStatus": "EXEMPT",
  "hiringManagerId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
  "jobProfileId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
  "regionId": "3fa85f64-5717-4562-b3fc-2c963f66afa6"
}
```

## Response

`200` Success

Under `data` (createPositionOutput):

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `id` | string | yes | The unique identifier for the created position. |

```json
{
  "data": {
    "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6"
  },
  "diagnostics": [
    {
      "code": "<code>",
      "message": "<message>",
      "severity": "error",
      "path": [
        "<path>"
      ],
      "details": "<details>"
    }
  ]
}
```

## Response headers

- `Idempotency-Replayed` — Present and `true` only when this response replays a previously stored one for the same Idempotency-Key, rather than reflecting a live execution. Absent on a live response - never sent as `false`.

## Errors

| Code | Status |
| --- | --- |
| `MANAGER_NOT_FOUND` | 400 |
| `JOB_PROFILE_NOT_FOUND` | 400 |
| `REGION_NOT_FOUND` | 400 |
| `DUPLICATE_POSITION` | 400 |
| `IDEMPOTENCY_KEY_CONFLICT` | 409 |
| `IDEMPOTENCY_PAYLOAD_MISMATCH` | 422 |

## Statuses

- `400` — Invalid request or business failure. Codes: MANAGER_NOT_FOUND, JOB_PROFILE_NOT_FOUND, REGION_NOT_FOUND, DUPLICATE_POSITION
- `401` — The request carries no valid access token.
- `403` — Not authorized
- `404` — Not found
- `409` — The Idempotency-Key is still being processed by another request.
- `422` — The Idempotency-Key was already used with a different request payload.
- `429` — Too many requests from this client address. The response has no body and no `Retry-After` header.
- `500` — Internal server error