> ## Documentation Index
> Fetch the complete documentation index at: https://docs.automate.ax/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Automate.ax automations are TypeScript programs.
> Use Bun for installation and command examples.
> Use Automate.ax for the product name and automate.ax for the package, CLI, and domain.
> Treat documented public APIs as current; do not invent transitional or deprecated names.

# List event types

> Lists personal Cal.com event types.

`calcom.listEventTypes` lists personal Cal.com event types.

```ts automations/list-event-types.automation.ts theme={null}
import { automation, markSignificant } from "automate.ax"
import { calcom } from "automate.ax/calcom"

export default automation("List event types", () => {
  markSignificant(
    calcom.listEventTypes({
      username: "ada",
      eventSlug: "intro",
      sortCreatedAt: "desc",
    }),
  )
})
```

## Input

| Field           | Type              | Required | Description                                  |
| --------------- | ----------------- | -------- | -------------------------------------------- |
| `eventSlug`     | `string`          | No       | Event slug; requires `username`.             |
| `orgId`         | `integer`         | No       | Organization ID.                             |
| `orgSlug`       | `string`          | No       | Organization slug.                           |
| `sortCreatedAt` | `"asc" \| "desc"` | No       | Creation order.                              |
| `username`      | `string`          | No       | Personal event owner.                        |
| `usernames`     | `string[]`        | No       | Dynamic event owners; requires at least two. |

## Output

Returns an array of matching personal or dynamic event types. Each typed item includes its required identity (`id`, `title`, `slug`, `ownerId`, and `bookingUrl`), duration, locations, booking fields, availability and booking limits, calendar behavior, owner users, and every supported event-type setting.

Cal.com enforces account role, plan, and availability requirements. Provider rejections surface as structured action failures with the HTTP status and any `Retry-After` delay.
