---
title: "List the archive’s labels"
method: GET
path: "/api/v1/rest/documents/labels"
tags: ["Documents"]
---

# List the archive’s labels

`GET /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

The tenant’s whole label tree («Etichette») — id, name, colour and parent — in tree order (a parent always precedes its children). Labels are metadata beside a document, not folders: a document may carry any number. Call this before documents_create_label (to nest under an existing one), documents_update_label, documents_delete_label or documents_set_labels — each needs an id or an exact name, and a name is unique only among its siblings, so two labels called «2026» under different parents are told apart by their id.

**Examples**

- What labels does the archive have?
  `GET /api/v1/rest/documents/labels`

## Headers

- `X-Tenant-Id` string, uuid

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