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

# Decline booking

> Declines a pending Cal.com booking.

`calcom.declineBooking` declines a pending Cal.com booking.

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

export default automation("Decline booking", () => {
  markSignificant(
    calcom.declineBooking({
      bookingUid: "booking-uid",
      reason: "Outside supported hours",
    }),
  )
})
```

## Input

Pass these fields:

| Field        | Type     | Required | Description                                                 |
| ------------ | -------- | -------- | ----------------------------------------------------------- |
| `bookingUid` | `string` | Yes      | —                                                           |
| `reason`     | `string` | No       | Reason for declining a booking that requires a confirmation |

## Output

The action removes the outer Cal.com status envelope. Its result is one of these data variants:

| Variant                  | Result                                                   |
| ------------------------ | -------------------------------------------------------- |
| Regular booking          | One booking object.                                      |
| Recurring booking        | One recurring booking object or an array of them.        |
| Seated booking           | One seated booking object.                               |
| Recurring seated booking | One recurring seated booking object or an array of them. |

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.