# Reject absence requests

Operation ID: `rejectAbsences`

Group: People Management › Absences

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

`POST /people/absences/reject`

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

Rejects one or more absence requests. Each absence must have status 'requested'. Unless you are an HR admin, each absence must also match an absence approval policy, you must be one of its approvers or the employee's direct manager, and it may not be your own absence. If any absence can't be rejected, none are.

The response lists the rejected absences' ids in the order you sent them.

## 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`: rejectAbsencesInput.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `absences` | array<object> | yes | The absences to reject. |
| `absences[].id` | string | yes | The unique identifier for the absence to reject. |
| `approverEmployeeId` | string | no | The unique identifier for the employee performing the rejection. Omit to let the platform infer it from the session. See id on GET people/person/:id. |

```json
{
  "absences": [
    {
      "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6"
    }
  ],
  "approverEmployeeId": "3fa85f64-5717-4562-b3fc-2c963f66afa6"
}
```

## Response

`200` Success

Under `data` (rejectAbsencesOutput):

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `ids` | array<string> | yes | The unique identifiers for the rejected absences, in the same order as the input. |

```json
{
  "data": {
    "ids": [
      "<ids>"
    ]
  },
  "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 |
| --- | --- |
| `NO_APPROVAL_POLICY` | 400 |
| `NOT_FOUND` | 400 |
| `EMPLOYEE_NOT_FOUND` | 400 |
| `ALREADY_DECIDED` | 400 |
| `IDEMPOTENCY_KEY_CONFLICT` | 409 |
| `IDEMPOTENCY_PAYLOAD_MISMATCH` | 422 |

## Statuses

- `400` — Invalid request or business failure. Codes: NO_APPROVAL_POLICY, NOT_FOUND, EMPLOYEE_NOT_FOUND, ALREADY_DECIDED
- `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