# List calendars

> Lists the calendars connected to your workspace that you can see, whether or not a receptionist books on them. An admin sees every calendar in the workspace…

`GET /v2/api/calendars`

<Note>
**Required scope:** `AGENTS_READ`
</Note>

## Behavior

Lists the calendars connected to your workspace, whether or not a receptionist books on them. Each `id` is what the `scheduling.calendars` map on [Update configuration](/docs/agent/update-agent) is keyed by.

The list is not paginated: it is bounded by your team, not by usage.

## What you can see

Visibility follows the same rule as the Allo app. An admin sees every calendar in the workspace, a team member only the ones they connected themselves. `owner.is_current_user` tells you which is which.

Connecting a calendar is an OAuth flow, done in the Allo app. This endpoint lists what is already connected.

## Event types

Event types are not in this response, because reading them costs one round trip to the provider per calendar. Fetch them one calendar at a time with [Get a calendar](/docs/agent/get-calendar).

## Errors

- `403 API_KEY_INSUFFICIENT_SCOPE`: the key does not hold `AGENTS_READ`.
