---
title: "Create a label"
method: POST
path: "/api/v1/rest/documents/labels"
tags: ["Documents"]
---

# Create a label

`POST /api/v1/rest/documents/labels`

## Request

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

Adds a label to the archive’s taxonomy. Nest it under an existing one with `parent_id` (from documents_list_labels) — up to three levels deep. This does not label any document — call documents_set_labels afterwards.

## Headers

- `X-Tenant-Id` string, uuid

## Request body

- object
  - `name` string, required
  - `color` 'slate' | 'red' | 'amber' | 'green' | 'teal' | 'blue' | 'violet' | 'pink'
  - `parent_id` string, uuid, nullable: Nest under this label. Omit for the top level.

## 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)