---
title: "Create a company closure"
method: POST
path: "/api/v1/rest/timbratura/closures"
tags: ["Time clock"]
---

# Create a company closure

`POST /api/v1/rest/timbratura/closures`

## Request

- Base URL: `https://api.custodo.ai`
- URL: `https://api.custodo.ai/api/v1/rest/timbratura/closures`
- Auth: HTTP bearer

A «Chiusura aziendale»: one approved absence for everybody it names (all, some sedi or some employees) between two dates, drawn from ferie or not. Days somebody already has off are skipped.

## Headers

- `X-Tenant-Id` string, uuid

## Request body

- object
  - `title` string, required
  - `from` string, date, required
  - `to` string, date, required
  - `deductFerie` boolean, required
  - `audience` 'all' | 'sites' | 'employees', required
  - `targets` string[]
  - `note` string, nullable

## Response `200`

Done. `data` is the tool’s own answer.

- RestResult
  - `ok` true, required
  - `data` unknown, required

## Other responses

- `400`: The arguments did not validate: `error.message` names the field, what it expects and what arrived.
- `401`: No API key, or one that is malformed, unknown, revoked or expired.
- `403`: The call never ran: the module is off for this organisation, the credential lacks the permission or the module, the tier does not cover it, or the tool is destructive and the key was not minted for that.
- `409`: The record is in a state that does not allow it — under legal hold, already sent, already closed. `error.code` says which.
- `422`: The tool ran and refused, in a sentence of its own (`TOOL_REFUSED`): the message says what to change. Retrying the same call will not help.
- `429`: The API key has spent its minute, or its day. Every request a key makes counts. See `Retry-After`.

---

[API](https://skmtc.dev/custodo/apis/custodo-integrazioni.md) · [All operations](https://skmtc.dev/custodo/apis/custodo-integrazioni/llms.txt) · [OpenAPI document](https://skmtc.dev/custodo/apis/custodo-integrazioni/revisions/16d336d3ec2a?raw)