---
title: "List calendars"
method: GET
path: "/api/v1/rest/calendario/calendars"
tags: ["Calendar"]
---

# List calendars

`GET /api/v1/rest/calendario/calendars`

## Request

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

The calendars the member behind this credential may use: their own personal one and every shared calendar opened to them, each with whether they may write on it. With `scope: all` and `calendario:company:read`, colleagues’ personal calendars too. Use an id from here as `calendar_id` when booking an event somewhere other than the member’s own calendar.

**Examples**

- Which calendars can I book on?
  `GET /api/v1/rest/calendario/calendars`

## Query parameters

- `scope` 'mine' | 'all'

## Headers

- `X-Tenant-Id` string, uuid

## Response `200`

Done. `data` is the tool’s answer, as described here. Its objects may carry fields this description does not name yet: read the ones you need and ignore the rest.

- object
  - `ok` true, required
  - `data` CalendarioListCalendarsResult, required
    - `items` object[], required
      - `id` string, required
      - `kind` 'personal' | 'shared', required
      - `name` string, nullable, required: Null on a personal calendar: it is «mine» to its owner.
      - `color` 'navy' | 'teal' | 'green' | 'amber' | 'red' | 'violet' | 'pink' | 'slate', required
      - `ownerUserId` string, nullable, required
      - `ownerName` string, nullable, required
      - `everyoneAccess` 'none' | 'read' | 'write', required
      - `archived` boolean, required
      - `canWrite` boolean, required
      - `canManage` boolean, required
      - `grants` object[]
        - `userId` string, nullable, required
        - `teamId` string, nullable, required
        - `name` string, required
        - `access` 'read' | 'write', 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)