---
ref: tool:cal-com/list-bookings
name: List bookings
company: company:cal-com
workflows: []
access: [mcp, cli, api]
tags: [capability:book-meetings, category:scheduling, has:api, has:cli, has:mcp]
docs: https://cal.com/docs/api-reference/v2/bookings/get-all-bookings
updated: 2026-09-27
---

# List bookings

Returns bookings filtered by status, attendee, event type and date range, one page at a time.

Filter by one `status` per request (`upcoming`, `past`, `cancelled`,
`recurring` or `unconfirmed`), by `attendeeEmail` to see whether a prospect
has booked, and by `afterStart` and `beforeEnd`. Over the API, send
`cal-api-version: 2026-05-01` and page with a cursor: pass
`pagination.nextCursor` back as `cursor` until `hasMore` is false. The CLI
pages with `--take` and `--skip`.

## Set up

Use the first option your agent supports.

### MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

```json
{ "mcpServers": { "cal-com": { "url": "https://mcp.cal.com/mcp" } } }
```

Call the MCP tool `get_bookings`.

Server URL: https://mcp.cal.com/mcp

### CLI (official)

Install the command, then confirm it runs.

```sh
npm install -g @calcom/cli
calcom --version
```

Run `calcom bookings list`.

Set `$CAL_API_KEY` in your environment first (get a key: https://app.cal.com/settings/developer/api-keys).

### API (official)

- Base URL: https://api.cal.com
- Endpoint: `GET /v2/bookings`
- Auth: send the header `Authorization: Bearer $CAL_API_KEY`
- Get a key: https://app.cal.com/settings/developer/api-keys
- Docs: https://cal.com/docs/api-reference/v2/introduction

Before doing anything else, make one read-only call to confirm access.

## Rules

- Ask the user before anything that sends messages, costs money, or changes data.
- Never print API keys.
