[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Add an absence

> Add a full-length absence for an employee in a unit. Inputs, cURL, Python and Node.js examples and an example response.

Source: https://cotlet.dev/docs/api/quinyx/add_absence

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

Add a full-length absence for an employee in a unit.

Quinyx API: https://cotlet.dev/docs/api/quinyx.md

`POST https://cotlet.dev/api/v1/quinyx/employees/{employee_id}/absences`

Access: write. Confirm: waits for the user's OK before it runs.

Does what the Add Absence panel does: it picks the employee, dates, absence type and who must approve, and saves. The response shows the employee's Time Tracker balance. Part-time absences, split per shift or per day, are not part of this tool. By default you confirm each call; you can switch that off for this tool.

## Parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `employee_id` | string | yes | Employee id from list_employees. |
| `group_id` | string | yes | Unit id from list_groups. |
| `start` | string | yes | Start, YYYY-MM-DD or YYYY-MM-DDTHH:MM. |
| `end` | string | yes | End, same format as start. |
| `absence_type` | string | yes | Name of an absence type your account has. |
| `all_day` | boolean | no | Treat the absence as whole days. Default false. |
| `approval` | string | no | Who must approve the absence: employee, manager or both. |
| `comment` | string | no | Optional comment. |

## Request

**cURL**

```bash
curl -X POST https://cotlet.dev/api/v1/quinyx/employees/employee_8c41d2/absences \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"group_id":"group_8c41d2","start":"start","end":"end","absence_type":"absence type"}'
```

**Python**

```python
result = client.call("quinyx", "add_absence", {"employee_id":"employee_8c41d2","group_id":"group_8c41d2","start":"start","end":"end","absence_type":"absence type"})
```

**Node.js**

```js
const result = await cotlet.call('quinyx', 'add_absence', {"employee_id":"employee_8c41d2","group_id":"group_8c41d2","start":"start","end":"end","absence_type":"absence type"});
```

**CLI**

```bash
cotlet call quinyx add_absence --data '{"employee_id":"employee_8c41d2","group_id":"group_8c41d2","start":"start","end":"end","absence_type":"absence type"}'
```

## Example response

```json
{
  "absence_id": "66104",
  "employee": "Maria Silva",
  "absence_type": "Sick leave",
  "start": "2026-10-26",
  "end": "2026-10-27",
  "all_day": true,
  "approval": "manager",
  "status": "saved"
}
```

Previous: [Offer an unassigned shift](https://cotlet.dev/docs/api/quinyx/offer_shift.md)
Next: [Create a shift](https://cotlet.dev/docs/api/quinyx/create_shift.md)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.