---
title: "client.bookings"
description: "Every method in this namespace: its signature, its parameters, what it returns and an example."
url: "https://openemail.uk/docs/ruby/reference/bookings"
area: "Ruby"
category: "Reference"
---

# client.bookings

Every method in this namespace: its signature, its parameters, what it returns and an example.

## Methods

Public links where somebody books a meeting on a person's calendar: create a booking page, change its hours, questions and rules, pause or delete it, read the times it offers, list the meetings guests booked, and approve, decline or cancel one. An API key acts for the workspace owner, and an app for the person who connected it.

### `bookings.list_pages`

List the booking pages of the person

```ruby
list_pages(api_key: nil) -> Array<Hash>
```

Returns every booking page of the person, oldest first. A booking page is a public link, `/book/<slug>`, where somebody picks a free time and books a meeting on the calendar of that person. Each page comes with its settings in `config`, the link to hand to guests in `url`, and in `counts` how many of its bookings are upcoming and how many wait for approval.

`status` is `active` while the page takes bookings and `paused` while its link works but offers no times. `problem` says what stops a page from taking bookings and is nil when nothing does. `away` lists the out of office periods that close the page. A person holds at most 25 pages, so the list comes whole and is never paged.

Scopes: `calendar:read`.

**Parameters**

- `api_key` (`String`): Overrides the client API key for this call only.

**Returns**

An Array of Hashes. Each item has `id`, `slug`, `name`, `status`, `url`, `problem`, `config`, `counts`, `away`, `createdAt` and `updatedAt`.

**Example**

```ruby
client.bookings.list_pages.each do |page|
  puts "#{page[:name]} #{page[:url]} #{page[:status]} #{page[:counts][:upcoming]} #{page[:counts][:pending]}"
end
```

**Notes**

- A booking page belongs to one person. An API key acts as the workspace owner and reaches the pages of the owner, and a connected app reaches the pages of the person who connected it.
- `problem` is `sender` when `config.fromEmail` can no longer send, `hours` when no hours are open at all, and `host` when the person left the workspace.
- A key or an app limited to particular addresses or domains is refused with 422 `capability_unsupported`, because a booking page reads the whole calendar of its person.

Also available in: API [`GET /booking-pages`](https://openemail.uk/docs/api/reference/booking-pages#get-booking-pages); TypeScript [`bookings.listPages()`](https://openemail.uk/docs/sdk/reference/bookings#listPages); Python [`bookings.list_pages()`](https://openemail.uk/docs/python/reference/bookings#listPages); PHP [`bookings->listPages`](https://openemail.uk/docs/php/reference/bookings#listPages); Go [`Bookings.ListPages`](https://openemail.uk/docs/go/reference/bookings#listPages); Java [`bookings().listPages`](https://openemail.uk/docs/java/reference/bookings#listPages); C# [`Bookings.ListPagesAsync`](https://openemail.uk/docs/csharp/reference/bookings#listPages); CLI [`openemail bookings list-pages`](https://openemail.uk/docs/cli/reference/bookings#bookings-list-pages).

### `bookings.get_page`

Read one booking page by id

```ruby
get_page(id, api_key: nil) -> Hash
```

Looks up a single booking page and returns it in the same shape as a row of `list_pages`, with every setting in `config`: the meeting lengths, where the meeting happens, the weekly hours and the dates with their own hours, the notice, the buffers and the daily limit, whether a booking waits for approval, the address its emails come from, the questions a guest is asked, how the page looks and what a guest may change afterwards.

`config.availability.weekly` holds seven lists, Sunday first, of the hours open on that weekday, each as minutes after midnight in `config.availability.timezone`. `problem` says what stops the page from taking bookings, and `away` lists the out of office periods of `config.fromEmail` that are running or still to come. While `config.busy.outOfOffice` is true the page offers no times inside them.

Scopes: `calendar:read`.

**Parameters**

- `id` (`String`, required): Booking page id such as `bkp_5c1e9a7b3d2f48e6a0b4c7d1`, as `list_pages` returns it.
- `api_key` (`String`): Overrides the client API key for this call only.

**Returns**

A Hash with `id`, `slug`, `name`, `status`, `url`, `problem`, `config`, `counts`, `away`, `createdAt` and `updatedAt`.

**Example**

```ruby
page = client.bookings.get_page("bkp_5c1e9a7b3d2f48e6a0b4c7d1")

puts page[:url], page[:problem]
p page[:config][:durations], page[:config][:availability][:timezone]
```

**Notes**

- A missing page raises `OpenEmail::ApiError` with `not_found?` true and code `booking_page_not_found`. A page that belongs to somebody else in the workspace is missing too.
- A booking page belongs to one person. An API key acts as the workspace owner and reaches the pages of the owner, and a connected app reaches the pages of the person who connected it.
- A key or an app limited to particular addresses or domains is refused with 422 `capability_unsupported`, because a booking page reads the whole calendar of its person.

Also available in: API [`GET /booking-pages/{id}`](https://openemail.uk/docs/api/reference/booking-pages#get-booking-pages-id); TypeScript [`bookings.getPage()`](https://openemail.uk/docs/sdk/reference/bookings#getPage); Python [`bookings.get_page()`](https://openemail.uk/docs/python/reference/bookings#getPage); PHP [`bookings->getPage`](https://openemail.uk/docs/php/reference/bookings#getPage); Go [`Bookings.GetPage`](https://openemail.uk/docs/go/reference/bookings#getPage); Java [`bookings().getPage`](https://openemail.uk/docs/java/reference/bookings#getPage); C# [`Bookings.GetPageAsync`](https://openemail.uk/docs/csharp/reference/bookings#getPage); CLI [`openemail bookings get-page`](https://openemail.uk/docs/cli/reference/bookings#bookings-get-page).

### `bookings.create_page`

Create a booking page

```ruby
create_page(body = nil, api_key: nil, **fields) -> Hash
```

Creates a booking page and returns it as it is stored. The page takes bookings at once, at the link in `url`. Only `name` is required: the page starts with weekdays from 09:00 to 17:00, 30 minute meetings, four hours of notice, times up to 60 days ahead and the first address the person may send from. Anything in `config` replaces that default, and what it leaves out keeps it.

`slug` is the last part of the public link, `/book/<slug>`. Left out, it is made from the name. `timezone` says which time zone the working hours are read in when `config.availability.timezone` is not sent.

The times a page offers are its working hours with everything taken out that makes the person busy: their calendar events, invitations they have not declined, calendars they subscribed to, bookings they already have, the gaps the page keeps around meetings, and the days they are out of office. A booking is a calendar event organised by `config.fromEmail`, and the guest is told by email from that address, so the call needs `emails:send` beside `calendar:write`.

Scopes: `calendar:write`, `emails:send`.

**Parameters**

- `name` (`String`, required): What the page is called, shown to guests as its heading, such as `Intro call`. Trimmed, 1 to 80 characters.
- `slug` (`String`): The last part of the public link: 3 to 60 lowercase letters and digits, with single hyphens between words. It is unique across OpenEmail. Left out, it is made from the name.
- `timezone` (`String`): The IANA time zone the working hours are read in, such as `Europe/Berlin`, when `config.availability.timezone` is not sent. Defaults to `UTC`.
- `config.description` (`String`): Text shown under the name of the page, up to 2,000 characters. Basic Markdown works: bold, italic, links and lists. Defaults to none.
- `config.hostName` (`String`): The name guests see as the person they meet, up to 80 characters. Defaults to the name of the account.
- `config.durations` (`Array<Integer>`): The meeting lengths a guest can pick, in minutes: 1 to 4 of them, each a multiple of 5 between 5 and 720. Defaults to `[30]`.
- `config.location.kind` (`String`): Where the meeting happens: `video` with a fixed link in `value`, `phone`, where the guest is asked for a number, `in-person` with the address in `value`, or `none`. Defaults to `none`.
- `config.location.value` (`String`): The `https://` link of a `video` meeting or the address of an `in-person` one, up to 500 characters. It is dropped for `phone` and `none`.
- `config.availability.timezone` (`String`): The IANA time zone the hours of the page are read in. Defaults to `timezone`.
- `config.availability.weekly` (`Array<Array<Hash>>`): Seven lists, Sunday first, of the hours open on that weekday. Each range is a Hash with `start` and `end` in minutes after midnight, so `{start: 540, end: 1020}` is 09:00 to 17:00. An empty list closes the day, and a day takes at most 6 ranges. Defaults to 09:00 to 17:00 from Monday to Friday.
- `config.availability.overrides` (`Array<Hash>`): Dates with their own hours, at most 180, each a Hash with `date` and `ranges`. `date` is `YYYY-MM-DD` in the time zone of the page, and an empty `ranges` closes that date. Defaults to none.
- `config.rules.noticeMinutes` (`Integer`): How many minutes ahead a booking has to be made, from 0 to 43,200. Defaults to 240.
- `config.rules.horizonDays` (`Integer`): How many days ahead the page offers times, from 1 to 365. Defaults to 60.
- `config.rules.intervalMinutes` (`Integer or nil`): Minutes between two start times: 5, 10, 15, 20, 30, 45, 60, 90 or 120. `nil`, the default, steps by the length of the meeting.
- `config.rules.bufferBeforeMinutes` (`Integer`): Minutes kept free before every meeting, from 0 to 240. Defaults to 0.
- `config.rules.bufferAfterMinutes` (`Integer`): Minutes kept free after every meeting, from 0 to 240. Defaults to 0.
- `config.rules.dailyLimit` (`Integer or nil`): The most bookings the page takes on one day, from 1 to 50. `nil`, the default, sets no limit.
- `config.approval` (`Boolean`): `true` holds each new booking as a request until `approve` or `decline` answers it. `false`, the default, confirms it at once.
- `config.fromEmail` (`String`): The address the booking emails are sent from and the calendar events are organised by. It has to be one the owner of the page may send from. Defaults to the first such address.
- `config.notifyHost` (`Boolean`): Whether `fromEmail` gets an email about each new, moved or cancelled booking. Defaults to true.
- `config.questions` (`Array<Hash>`): What the guest is asked besides their name and email, at most 10, each a Hash with `id`, `kind`, `label`, `required` and `options`. `id` is a stable key for the answers: 4 to 16 lowercase letters and digits, unique on the page. `kind` is `text`, `long-text`, `phone`, `choice` or `checkbox`. `options` holds the answers of a `choice` question, from 2 to 12, and is empty for the other kinds. Defaults to none.
- `config.confirmation` (`String`): Text shown to the guest after booking and added to the confirmation email, up to 1,000 characters. Defaults to none.
- `config.redirectUrl` (`String`): An `https://` page to send the guest to after booking, or an empty string for none, which is the default.
- `config.appearance.accent` (`String`): The colour of buttons and the picked day, as `#rrggbb`. Defaults to `#18181b`.
- `config.appearance.theme` (`String`): `auto` follows the device of the guest, and `light` or `dark` forces one. Defaults to `auto`.
- `config.appearance.showAvatar` (`Boolean`): Whether the page shows the photo of the person, or their initials when they have none. Defaults to true.
- `config.guestChanges.cancel` (`Boolean`): Whether a guest may cancel from the link in their emails. Defaults to true.
- `config.guestChanges.reschedule` (`Boolean`): Whether a guest may move the meeting from the link in their emails. Defaults to true.
- `config.guestChanges.cutoffMinutes` (`Integer`): How many minutes before the meeting those changes close, from 0 to 20,160. Defaults to 0.
- `config.busy.addresses` (`Array<String> or nil`): The addresses whose invitations block time unless declined, at most 50. `nil`, the default, checks every address the person holds.
- `config.busy.subscriptions` (`Boolean`): Whether events from calendars the person subscribed to block time. Defaults to true.
- `config.busy.outOfOffice` (`Boolean`): Whether the page offers no times while `fromEmail` is out of office. Defaults to true.
- `config.seo.title` (`String`): The title of the browser tab and of a search result, up to 120 characters. Empty, the default, uses the name of the page and the host.
- `config.seo.description` (`String`): The summary under the title in a search result, up to 300 characters. Empty, the default, uses the start of the description.
- `config.seo.indexable` (`Boolean`): Whether search engines may list the page. Defaults to false, which asks them not to.
- `config.extraGuests` (`Integer`): How many other people a guest may add to a booking, 0 to 10. Each one gets the invitation and every later change. Defaults to 0, which hides the field.
- `api_key` (`String`): Overrides the client API key for this call only.

**Returns**

A Hash with the new `id`, `status` `active`, the `slug` and `url` of its link, and `config` with every default filled in.

**Example**

```ruby
page = client.bookings.create_page(
  name: "Intro call",
  timezone: "Europe/Berlin",
  config: {
    description: "A first conversation about your project.",
    durations: [30, 60],
    location: {kind: "video", value: "https://meet.example.com/ada"},
    rules: {bufferAfterMinutes: 15},
    approval: true
  }
)

puts page[:id], page[:url], page[:config][:fromEmail]
```

**Notes**

- A booking page belongs to one person. An API key acts as the workspace owner and makes a page of the owner, and a connected app makes a page of the person who connected it.
- A person holds at most 25 pages. One more is a 403 `booking_page_limit_reached`.
- A `slug` another page already uses is a 409 `booking_link_taken`. A slug that is not a valid link, a `fromEmail` the person may not send from, a `video` location without a link, an `in-person` one without an address and two questions with the same `id` are 422 `invalid_booking_page`, with the reason in the message. A few slugs such as `manage` and `admin` are reserved.
- A value of the wrong type or length, a range that ends before it starts and a time zone in `config.availability` that is not known are 422 `invalid_parameter` with `param` naming the field. A key beside `name`, `slug`, `timezone` and `config` is 422 `unknown_parameter`.
- A key or an app limited to particular addresses or domains is refused with 422 `capability_unsupported`, because a booking page reads the whole calendar of its person.
- Not retried automatically. A slug made from the name gets a few random characters when the plain one is taken, so a retry after a lost response can leave two pages. List them and delete the spare.

Also available in: API [`POST /booking-pages`](https://openemail.uk/docs/api/reference/booking-pages#post-booking-pages); TypeScript [`bookings.createPage()`](https://openemail.uk/docs/sdk/reference/bookings#createPage); Python [`bookings.create_page()`](https://openemail.uk/docs/python/reference/bookings#createPage); PHP [`bookings->createPage`](https://openemail.uk/docs/php/reference/bookings#createPage); Go [`Bookings.CreatePage`](https://openemail.uk/docs/go/reference/bookings#createPage); Java [`bookings().createPage`](https://openemail.uk/docs/java/reference/bookings#createPage); C# [`Bookings.CreatePageAsync`](https://openemail.uk/docs/csharp/reference/bookings#createPage); CLI [`openemail bookings create-page`](https://openemail.uk/docs/cli/reference/bookings#bookings-create-page).

### `bookings.update_page`

Change the name, the link, the status or any setting of a booking page

```ruby
update_page(id, patch = nil, api_key: nil, **fields) -> Hash
```

Changes a booking page and returns it as it is stored. Send only what changes: a field left out stays as it is, and a patch with nothing in it is a 422.

`config` is merged, not replaced. A top-level value such as `approval` or `fromEmail` replaces the stored one. Inside `location`, `availability`, `rules`, `appearance`, `guestChanges`, `busy` and `seo` each field is merged on its own, so `rules: {dailyLimit: 4}` leaves the notice and the buffers alone. A list is replaced whole: send every entry of `durations`, `questions`, `availability.weekly` or `availability.overrides` again, not only the ones that change.

Set `status` to `paused` to stop offering times without losing the link, and to `active` to offer them again. Bookings already made keep their time whatever changes. A new `slug` moves the page to a new link and the old one stops working, so links already handed out break.

Scopes: `calendar:write`, `emails:send`.

**Parameters**

- `id` (`String`, required): Booking page id such as `bkp_5c1e9a7b3d2f48e6a0b4c7d1`, as `list_pages` returns it.
- `name` (`String`): New name, shown to guests as the heading of the page. Trimmed, 1 to 80 characters. Left out, the name stays.
- `slug` (`String`): New last part of the public link: 3 to 60 lowercase letters and digits, with single hyphens between words. It is unique across OpenEmail. Left out, the link stays.
- `status` (`String`): `active` takes bookings. `paused` keeps the link working but offers no times. Left out, it stays.
- `config.description` (`String`): Text shown under the name of the page, up to 2,000 characters. Basic Markdown works: bold, italic, links and lists. An empty string clears it.
- `config.hostName` (`String`): The name guests see as the person they meet, up to 80 characters.
- `config.durations` (`Array<Integer>`): The meeting lengths a guest can pick, in minutes, replacing the list the page had: 1 to 4 of them, each a multiple of 5 between 5 and 720.
- `config.location.kind` (`String`): Where the meeting happens: `video` with a fixed link in `value`, `phone`, where the guest is asked for a number, `in-person` with the address in `value`, or `none`.
- `config.location.value` (`String`): The `https://` link of a `video` meeting or the address of an `in-person` one, up to 500 characters. It is dropped for `phone` and `none`.
- `config.availability.timezone` (`String`): The IANA time zone the hours of the page are read in, such as `Europe/Berlin`.
- `config.availability.weekly` (`Array<Array<Hash>>`): All seven lists again, Sunday first, of the hours open on that weekday. Each range is a Hash with `start` and `end` in minutes after midnight, so `{start: 540, end: 1020}` is 09:00 to 17:00. An empty list closes the day, and a day takes at most 6 ranges.
- `config.availability.overrides` (`Array<Hash>`): Every date with its own hours again, at most 180, each a Hash with `date` and `ranges`. `date` is `YYYY-MM-DD` in the time zone of the page, and an empty `ranges` closes that date. An empty array removes them all.
- `config.rules.noticeMinutes` (`Integer`): How many minutes ahead a booking has to be made, from 0 to 43,200.
- `config.rules.horizonDays` (`Integer`): How many days ahead the page offers times, from 1 to 365.
- `config.rules.intervalMinutes` (`Integer or nil`): Minutes between two start times: 5, 10, 15, 20, 30, 45, 60, 90 or 120. `nil` steps by the length of the meeting.
- `config.rules.bufferBeforeMinutes` (`Integer`): Minutes kept free before every meeting, from 0 to 240.
- `config.rules.bufferAfterMinutes` (`Integer`): Minutes kept free after every meeting, from 0 to 240.
- `config.rules.dailyLimit` (`Integer or nil`): The most bookings the page takes on one day, from 1 to 50. `nil` sets no limit.
- `config.approval` (`Boolean`): `true` holds each new booking as a request until `approve` or `decline` answers it. `false` confirms it at once. Requests already waiting keep waiting.
- `config.fromEmail` (`String`): The address the booking emails are sent from and the calendar events are organised by. It has to be one the owner of the page may send from.
- `config.notifyHost` (`Boolean`): Whether `fromEmail` gets an email about each new, moved or cancelled booking.
- `config.questions` (`Array<Hash>`): Every question again, at most 10, each a Hash with `id`, `kind`, `label`, `required` and `options`. `id` is a stable key for the answers: 4 to 16 lowercase letters and digits, unique on the page. `kind` is `text`, `long-text`, `phone`, `choice` or `checkbox`. `options` holds the answers of a `choice` question, from 2 to 12, and is empty for the other kinds. An empty array asks nothing more.
- `config.confirmation` (`String`): Text shown to the guest after booking and added to the confirmation email, up to 1,000 characters. An empty string clears it.
- `config.redirectUrl` (`String`): An `https://` page to send the guest to after booking, or an empty string for none.
- `config.appearance.accent` (`String`): The colour of buttons and the picked day, as `#rrggbb`.
- `config.appearance.theme` (`String`): `auto` follows the device of the guest, and `light` or `dark` forces one.
- `config.appearance.showAvatar` (`Boolean`): Whether the page shows the photo of the person, or their initials when they have none.
- `config.guestChanges.cancel` (`Boolean`): Whether a guest may cancel from the link in their emails.
- `config.guestChanges.reschedule` (`Boolean`): Whether a guest may move the meeting from the link in their emails.
- `config.guestChanges.cutoffMinutes` (`Integer`): How many minutes before the meeting those changes close, from 0 to 20,160.
- `config.busy.addresses` (`Array<String> or nil`): The addresses whose invitations block time unless declined, at most 50. `nil` checks every address the person holds.
- `config.busy.subscriptions` (`Boolean`): Whether events from calendars the person subscribed to block time.
- `config.busy.outOfOffice` (`Boolean`): Whether the page offers no times while `fromEmail` is out of office.
- `config.seo.title` (`String`): The title of the browser tab and of a search result, up to 120 characters. An empty string goes back to the name of the page and the host.
- `config.seo.description` (`String`): The summary under the title in a search result, up to 300 characters. An empty string goes back to the start of the description.
- `config.seo.indexable` (`Boolean`): Whether search engines may list the page.
- `config.extraGuests` (`Integer`): How many other people a guest may add to a booking, 0 to 10. Each one gets the invitation and every later change. 0 hides the field.
- `api_key` (`String`): Overrides the client API key for this call only.

**Returns**

A Hash with the unchanged `id`, and everything else as it is now.

**Example**

```ruby
page = client.bookings.update_page(
  "bkp_5c1e9a7b3d2f48e6a0b4c7d1",
  config: {
    durations: [45],
    rules: {bufferAfterMinutes: 15, dailyLimit: 4}
  }
)

p page[:config][:durations], page[:config][:rules]
```

**Notes**

- A missing page is a 404 `booking_page_not_found`, and so is a page that belongs to somebody else in the workspace.
- A `slug` another page already uses is a 409 `booking_link_taken`. A slug that is not a valid link, a `fromEmail` the person may not send from, a `video` location without a link, an `in-person` one without an address and two questions with the same `id` are 422 `invalid_booking_page`, with the reason in the message.
- An empty patch, a value of the wrong type or length, a range that ends before it starts and a time zone that is not known are 422 `invalid_parameter`. A key beside `name`, `slug`, `status` and `config` is 422 `unknown_parameter`.
- A booking page belongs to one person. An API key acts as the workspace owner and reaches the pages of the owner, and a connected app reaches the pages of the person who connected it.
- A key or an app limited to particular addresses or domains is refused with 422 `capability_unsupported`, because a booking page reads the whole calendar of its person.
- The SDK retries this call after a network failure, since the same patch sent twice leaves the same page.

Also available in: API [`PATCH /booking-pages/{id}`](https://openemail.uk/docs/api/reference/booking-pages#patch-booking-pages-id); TypeScript [`bookings.updatePage()`](https://openemail.uk/docs/sdk/reference/bookings#updatePage); Python [`bookings.update_page()`](https://openemail.uk/docs/python/reference/bookings#updatePage); PHP [`bookings->updatePage`](https://openemail.uk/docs/php/reference/bookings#updatePage); Go [`Bookings.UpdatePage`](https://openemail.uk/docs/go/reference/bookings#updatePage); Java [`bookings().updatePage`](https://openemail.uk/docs/java/reference/bookings#updatePage); C# [`Bookings.UpdatePageAsync`](https://openemail.uk/docs/csharp/reference/bookings#updatePage); CLI [`openemail bookings update-page`](https://openemail.uk/docs/cli/reference/bookings#bookings-update-page).

### `bookings.delete_page`

Delete a booking page

```ruby
delete_page(id, api_key: nil) -> Hash
```

Deletes a booking page for good. Its public link stops working and the list of its bookings goes with it, so `list` no longer shows them and guests can no longer move or cancel through the links in their emails. The meetings already booked stay on the calendar, where `calendar.cancel_event` can still call one off.

There is no undo. To stop offering times and keep the page, its link and its bookings, use `update_page` with `status` `paused`.

Scopes: `calendar:write`.

**Parameters**

- `id` (`String`, required): Booking page id such as `bkp_5c1e9a7b3d2f48e6a0b4c7d1`, as `list_pages` returns it.
- `api_key` (`String`): Overrides the client API key for this call only.

**Returns**

A Hash with `object` set to `booking_page`, `id` and `deleted` set to true.

**Example**

```ruby
removed = client.bookings.delete_page("bkp_5c1e9a7b3d2f48e6a0b4c7d1")

puts removed[:id], removed[:deleted]
```

**Notes**

- It sends no email, so it needs `calendar:write` alone. Guests are not told that the page is gone.
- The SDK does not retry a delete. A 404 `booking_page_not_found` on your own second attempt after a lost response means the first one worked.
- A booking page belongs to one person. An API key acts as the workspace owner and reaches the pages of the owner, and a connected app reaches the pages of the person who connected it.
- A key or an app limited to particular addresses or domains is refused with 422 `capability_unsupported`, because a booking page reads the whole calendar of its person.

Also available in: API [`DELETE /booking-pages/{id}`](https://openemail.uk/docs/api/reference/booking-pages#delete-booking-pages-id); TypeScript [`bookings.deletePage()`](https://openemail.uk/docs/sdk/reference/bookings#deletePage); Python [`bookings.delete_page()`](https://openemail.uk/docs/python/reference/bookings#deletePage); PHP [`bookings->deletePage`](https://openemail.uk/docs/php/reference/bookings#deletePage); Go [`Bookings.DeletePage`](https://openemail.uk/docs/go/reference/bookings#deletePage); Java [`bookings().deletePage`](https://openemail.uk/docs/java/reference/bookings#deletePage); C# [`Bookings.DeletePageAsync`](https://openemail.uk/docs/csharp/reference/bookings#deletePage); CLI [`openemail bookings delete-page`](https://openemail.uk/docs/cli/reference/bookings#bookings-delete-page).

### `bookings.list_times`

List the times a booking page offers

```ruby
list_times(id, from: nil, to: nil, duration_minutes: nil, api_key: nil) -> Hash
```

Returns the start times a guest could book on a page inside a window, in order. They are the hours of the page with everything taken out that makes the person busy: their calendar events, invitations they have not declined, calendars they subscribed to, bookings they already have, the gaps the page keeps around meetings, its daily limit, its notice and the out of office periods that close it.

The window starts at `from`, or now, and ends at `to`, or 14 days later. It covers at most 62 days, and a later `to` is cut back to that. `duration_minutes:` picks which meeting length the times are for and has to be one of the `durations` of the page. Left out, the shortest is used. Both bounds take a Time, DateTime, Date or ISO 8601 String, and the SDK sends a Time or DateTime as a UTC ISO 8601 instant.

A paused page still answers, so the times can be checked before it is turned on. A page with a `problem` offers nothing.

Scopes: `calendar:read`.

**Parameters**

- `id` (`String`, required): Booking page id such as `bkp_5c1e9a7b3d2f48e6a0b4c7d1`, as `list_pages` returns it.
- `from` (`Time, DateTime, Date or String`): The start of the window. Defaults to now.
- `to` (`Time, DateTime, Date or String`): The end of the window, later than `from`. Defaults to 14 days after `from`, and counts for at most 62 days after it.
- `duration_minutes` (`Integer`): The meeting length in minutes, one of the `durations` of the page. Defaults to the shortest.
- `api_key` (`String`): Overrides the client API key for this call only.

**Returns**

A Hash with `pageId`, the `timezone` of the page, the `durationMinutes` the times are for, and `times`, every open start time in the window as an ISO 8601 instant in UTC.

**Example**

```ruby
from = Time.now
to = from + 7 * 24 * 60 * 60

offered = client.bookings.list_times("bkp_5c1e9a7b3d2f48e6a0b4c7d1", from:, to:, duration_minutes: 30)

offered[:times].each { |time| puts time }
```

**Notes**

- A `to` that is not later than `from` and a `duration_minutes:` the page does not offer are 422 `invalid_parameter`. A missing page is a 404 `booking_page_not_found`.
- The times are instants, so show them to a person in a time zone: `timezone` names the one the hours of the page are read in.
- It reads the calendar as it is now and holds nothing. A time it lists can be gone a moment later, when a guest books it.
- A booking page belongs to one person. An API key acts as the workspace owner and reaches the pages of the owner, and a connected app reaches the pages of the person who connected it.
- A key or an app limited to particular addresses or domains is refused with 422 `capability_unsupported`, because a booking page reads the whole calendar of its person.

Also available in: API [`GET /booking-pages/{id}/times`](https://openemail.uk/docs/api/reference/booking-pages#get-booking-pages-id-times); TypeScript [`bookings.listTimes()`](https://openemail.uk/docs/sdk/reference/bookings#listTimes); Python [`bookings.list_times()`](https://openemail.uk/docs/python/reference/bookings#listTimes); PHP [`bookings->listTimes`](https://openemail.uk/docs/php/reference/bookings#listTimes); Go [`Bookings.ListTimes`](https://openemail.uk/docs/go/reference/bookings#listTimes); Java [`bookings().listTimes`](https://openemail.uk/docs/java/reference/bookings#listTimes); C# [`Bookings.ListTimesAsync`](https://openemail.uk/docs/csharp/reference/bookings#listTimes); CLI [`openemail bookings list-times`](https://openemail.uk/docs/cli/reference/bookings#bookings-list-times).

### `bookings.list`

List the meetings guests booked, a page at a time

```ruby
list(view: nil, page_id: nil, limit: nil, cursor: nil, api_key: nil) -> OpenEmail::Page
```

Returns one page of bookings: the meetings guests booked on the booking pages of the person, or on one page with `page_id:`. `list_all` collects every page and `iterate` walks them lazily. A booking is a calendar event with the guest invited, so it shows wherever the calendar does, and a meeting moved or cancelled in the calendar reads as moved or cancelled here.

`view:` picks which bookings are listed. `upcoming`, the default, holds the confirmed meetings that are not over. `pending` holds the requests that wait for `approve` or `decline`, on a page whose `config.approval` is true. `past` holds the meetings that are over and the requests nobody answered in time, and `ended` holds the ones that were declined or cancelled. `upcoming` and `pending` come soonest first, `past` and `ended` latest first.

Each booking names its page in `pageId` and `pageName`, the guest in `guest`, what they answered in `answers` and its calendar event in `eventId`.

Scopes: `calendar:read`.

**Parameters**

- `view` (`String`): Which bookings to list: `upcoming`, `pending`, `past` or `ended`. Defaults to `upcoming`.
- `page_id` (`String`): Only the bookings of this booking page, by its id. Left out, the bookings of every page of the person are listed.
- `limit` (`Integer`): Page size, from 1 to 100. The server defaults to 30.
- `cursor` (`String`): The `next_cursor` of the previous page, passed back as it came. Leave it out for the first page.
- `api_key` (`String`): Overrides the client API key for this call only.

**Returns**

An `OpenEmail::Page` of Hashes, with `items`, `has_more?` and `next_cursor`. Each item has `id`, `pageId`, `pageName`, `status`, `expired`, `past`, `start`, `end`, `durationMinutes`, `guest`, `answers`, `location`, `eventId`, `endedBy`, `endReason`, `rescheduleCount`, `guestMailFailed` and `createdAt`.

**Example**

```ruby
page = client.bookings.list(view: "pending")

page.items.each do |booking|
  puts "#{booking[:id]} #{booking[:pageName]} #{booking[:guest][:name]} #{booking[:start]}"
end
```

**Notes**

- `status` is `pending` while a booking waits for approval, `confirmed` once the meeting stands, `declined` when a request was turned down and `cancelled` when a confirmed meeting was called off. `expired` is true for a request nobody answered before its time came, and `past` once the meeting is over.
- A `page_id:` that is not a page of the person answers 404 `booking_page_not_found`, and a cursor this list did not hand out 400 `invalid_cursor`.
- The cursor marks how far into the view the last page reached. A booking that enters or leaves the view between two pages shifts the rows after it, so read the view again when an exact list matters.
- An API key acts as the workspace owner and reads the bookings of the owner, and a connected app reads the bookings of the person who connected it. One guest address holds at most 3 upcoming bookings on a page.
- A key or an app limited to particular addresses or domains is refused with 422 `capability_unsupported`, because a booking page reads the whole calendar of its person.

Also available in: API [`GET /bookings`](https://openemail.uk/docs/api/reference/booking-pages#get-bookings); TypeScript [`bookings.list()`](https://openemail.uk/docs/sdk/reference/bookings#list); Python [`bookings.list()`](https://openemail.uk/docs/python/reference/bookings#list); PHP [`bookings->list`](https://openemail.uk/docs/php/reference/bookings#list); Go [`Bookings.List`](https://openemail.uk/docs/go/reference/bookings#list); Java [`bookings().list`](https://openemail.uk/docs/java/reference/bookings#list); C# [`Bookings.ListAsync`](https://openemail.uk/docs/csharp/reference/bookings#list); CLI [`openemail bookings list`](https://openemail.uk/docs/cli/reference/bookings#bookings-list).

### `bookings.list_all`

Collect every booking of a view into one array

```ruby
list_all(view: nil, page_id: nil, limit: nil, cursor: nil, api_key: nil) -> Array<Hash>
```

Walks every page of `list` and returns all bookings of one view, in the order of that view: `upcoming` and `pending` soonest first, `past` and `ended` latest first. One request per page. Give `page_id:` to collect only the bookings of one booking page.

Scopes: `calendar:read`.

**Parameters**

- `view` (`String`): Which bookings to collect: `upcoming`, `pending`, `past` or `ended`. Defaults to `upcoming`.
- `page_id` (`String`): Only the bookings of this booking page, by its id. Left out, the bookings of every page of the person are collected.
- `limit` (`Integer`): Page size for each request, from 1 to 100. The server defaults to 30.
- `cursor` (`String`): Starts the walk after this cursor instead of the first page.
- `api_key` (`String`): Overrides the client API key for every page of this walk.

**Returns**

An Array of Hashes holding every booking of the view.

**Example**

```ruby
bookings = client.bookings.list_all(view: "upcoming", limit: 100)
unsent = bookings.select { |booking| booking[:guestMailFailed] }

unsent.each { |booking| puts "#{booking[:id]} #{booking[:guest][:email]} #{booking[:start]}" }
```

**Notes**

- If any page fails the call raises and the bookings already fetched are discarded.
- The `past` and `ended` views grow without end, so prefer `iterate` there and stop when you have read far enough back.
- A key or an app limited to particular addresses or domains is refused with 422 `capability_unsupported`, because a booking page reads the whole calendar of its person.

Also available in: API [`GET /bookings`](https://openemail.uk/docs/api/reference/booking-pages#get-bookings); TypeScript [`bookings.listAll()`](https://openemail.uk/docs/sdk/reference/bookings#listAll); Python [`bookings.list_all()`](https://openemail.uk/docs/python/reference/bookings#listAll); PHP [`bookings->listAll`](https://openemail.uk/docs/php/reference/bookings#listAll); Go [`Bookings.ListAll`](https://openemail.uk/docs/go/reference/bookings#listAll); Java [`bookings().listAll`](https://openemail.uk/docs/java/reference/bookings#listAll); C# [`Bookings.ListAllAsync`](https://openemail.uk/docs/csharp/reference/bookings#listAll).

### `bookings.iterate`

Stream the bookings of a view one at a time

```ruby
iterate(view: nil, page_id: nil, limit: nil, cursor: nil, api_key: nil, &block) -> Enumerator<Hash>
```

Returns an Enumerator that yields the bookings of one view individually, in the order of that view, and requests the next page only once the current one is drained. Given a block, it yields each booking to the block instead. Nothing is fetched until you consume it, and breaking out of the loop stops the requests.

Scopes: `calendar:read`.

**Parameters**

- `view` (`String`): Which bookings to walk: `upcoming`, `pending`, `past` or `ended`. Defaults to `upcoming`.
- `page_id` (`String`): Only the bookings of this booking page, by its id. Left out, the bookings of every page of the person are walked.
- `limit` (`Integer`): Page size for each request, from 1 to 100. The server defaults to 30.
- `cursor` (`String`): Starts the walk after this cursor instead of the first page.
- `api_key` (`String`): Overrides the client API key for every page of this walk.

**Returns**

An Enumerator of Hashes, one booking per step (or yields each one to a block).

**Example**

```ruby
client.bookings.iterate(view: "ended") do |booking|
  puts "#{booking[:start]} #{booking[:pageName]} #{booking[:endedBy]} #{booking[:endReason]}"
end
```

**Notes**

- The Enumerator is lazy, so an abandoned loop costs only the pages you consumed.
- A key or an app limited to particular addresses or domains is refused with 422 `capability_unsupported`, because a booking page reads the whole calendar of its person.

Also available in: API [`GET /bookings`](https://openemail.uk/docs/api/reference/booking-pages#get-bookings); TypeScript [`bookings.iterate()`](https://openemail.uk/docs/sdk/reference/bookings#iterate); Python [`bookings.iterate()`](https://openemail.uk/docs/python/reference/bookings#iterate); PHP [`bookings->iterate`](https://openemail.uk/docs/php/reference/bookings#iterate); Go [`Bookings.Iterate`](https://openemail.uk/docs/go/reference/bookings#iterate); Java [`bookings().iterate`](https://openemail.uk/docs/java/reference/bookings#iterate); C# [`Bookings.IterateAsync`](https://openemail.uk/docs/csharp/reference/bookings#iterate).

### `bookings.get`

Read one booking by id

```ruby
get(id, api_key: nil) -> Hash
```

Looks up a single booking and returns it in the same shape as a row of `list`: the booking page it was made on, the guest with the time zone they booked in, what they answered to the questions of the page, where the meeting happens as the guest was told, the calendar event it is and how it ended if it did.

A booking follows its calendar event. Reading one first catches up with the calendar, so a meeting that was moved there shows its new `start` and `end`, and one that was cancelled or deleted there reads `cancelled`, or `declined` when it still waited for approval. `endedBy` says whether the `host` or the `guest` declined or cancelled it, and `endReason` holds the reason they gave. `guestMailFailed` is true when the last email to the guest could not be sent, and `resend_email` tries again.

Scopes: `calendar:read`.

**Parameters**

- `id` (`String`, required): Booking id such as `bkg_2b8d4f6a1c3e5079b6d8f0a2`, as `list` returns it.
- `api_key` (`String`): Overrides the client API key for this call only.

**Returns**

A Hash with `id`, `pageId`, `pageName`, `status`, `expired`, `past`, `start`, `end`, `durationMinutes`, `guest`, `answers`, `location`, `eventId`, `endedBy`, `endReason`, `rescheduleCount`, `guestMailFailed` and `createdAt`.

**Example**

```ruby
booking = client.bookings.get("bkg_2b8d4f6a1c3e5079b6d8f0a2")

puts booking[:status], booking[:start], booking[:guest][:name], booking[:guest][:email]

booking[:answers].each { |answer| puts "#{answer[:label]} #{answer[:value]}" }
```

**Notes**

- A missing booking raises `OpenEmail::ApiError` with `not_found?` true and code `booking_not_found`. A booking on a page that belongs to somebody else in the workspace is missing too.
- `eventId` is the id `calendar.get_event` reads. It is nil once the booking ended and its event was removed.
- Each answer carries the `id`, `label` and `kind` of its question as it was asked, and its `value` as text. A `checkbox` answers `yes` or `no`.
- An API key acts as the workspace owner and reads the bookings of the owner, and a connected app reads the bookings of the person who connected it.
- A key or an app limited to particular addresses or domains is refused with 422 `capability_unsupported`, because a booking page reads the whole calendar of its person.

Also available in: API [`GET /bookings/{id}`](https://openemail.uk/docs/api/reference/booking-pages#get-bookings-id); TypeScript [`bookings.get()`](https://openemail.uk/docs/sdk/reference/bookings#get); Python [`bookings.get()`](https://openemail.uk/docs/python/reference/bookings#get); PHP [`bookings->get`](https://openemail.uk/docs/php/reference/bookings#get); Go [`Bookings.Get`](https://openemail.uk/docs/go/reference/bookings#get); Java [`bookings().get`](https://openemail.uk/docs/java/reference/bookings#get); C# [`Bookings.GetAsync`](https://openemail.uk/docs/csharp/reference/bookings#get); CLI [`openemail bookings get`](https://openemail.uk/docs/cli/reference/bookings#bookings-get).

### `bookings.approve`

Confirm a booking that waits for approval

```ruby
approve(id, api_key: nil) -> Hash
```

Confirms a booking that waits for approval, on a booking page whose `config.approval` is true. The hold on the calendar becomes a confirmed meeting, and the guest is told by email, sent from the address of the page with the calendar invitation attached. It takes no body.

The email goes out as `config.fromEmail`, so the call needs `emails:send` beside `calendar:write`. `list` with `view: "pending"` reads the bookings that wait.

Scopes: `calendar:write`, `emails:send`.

**Parameters**

- `id` (`String`, required): Booking id such as `bkg_2b8d4f6a1c3e5079b6d8f0a2`, as `list` returns it.
- `api_key` (`String`): Overrides the client API key for this call only.

**Returns**

A Hash with `status` `confirmed`, and `guestMailFailed` saying whether the email to the guest went out.

**Example**

```ruby
booking = client.bookings.approve("bkg_2b8d4f6a1c3e5079b6d8f0a2")

puts booking[:status], booking[:start], booking[:guestMailFailed]
```

**Notes**

- A booking that is not waiting for approval answers 409 `booking_not_pending`, and one whose time has passed 409 `booking_ended`. A missing one is a 404 `booking_not_found`.
- The booking is confirmed even when the email cannot be sent. `guestMailFailed` is then true, and `resend_email` sends it again.
- An API key acts as the workspace owner and reaches the bookings of the owner, and a connected app reaches the bookings of the person who connected it.
- A key or an app limited to particular addresses or domains is refused with 422 `capability_unsupported`, because a booking page reads the whole calendar of its person.
- The SDK does not retry it, because a retry could email the guest twice. A 409 `booking_not_pending` on your own second attempt after a lost response means the first one worked or the guest withdrew, and `get` says which.

Also available in: API [`POST /bookings/{id}/approve`](https://openemail.uk/docs/api/reference/booking-pages#post-bookings-id-approve); TypeScript [`bookings.approve()`](https://openemail.uk/docs/sdk/reference/bookings#approve); Python [`bookings.approve()`](https://openemail.uk/docs/python/reference/bookings#approve); PHP [`bookings->approve`](https://openemail.uk/docs/php/reference/bookings#approve); Go [`Bookings.Approve`](https://openemail.uk/docs/go/reference/bookings#approve); Java [`bookings().approve`](https://openemail.uk/docs/java/reference/bookings#approve); C# [`Bookings.ApproveAsync`](https://openemail.uk/docs/csharp/reference/bookings#approve); CLI [`openemail bookings approve`](https://openemail.uk/docs/cli/reference/bookings#bookings-approve).

### `bookings.decline`

Turn down a booking that waits for approval

```ruby
decline(id, body = nil, api_key: nil, **fields) -> Hash
```

Turns down a booking that waits for approval and frees its time, so the page offers that time again. The guest is told by email, sent from the address of the page, with `reason` in it when one is given. Call it with the id alone to decline without a reason.

The email goes out as `config.fromEmail`, so the call needs `emails:send` beside `calendar:write`.

Scopes: `calendar:write`, `emails:send`.

**Parameters**

- `id` (`String`, required): Booking id such as `bkg_2b8d4f6a1c3e5079b6d8f0a2`, as `list` returns it.
- `reason` (`String or nil`): A sentence for the guest, trimmed, at most 500 characters, included in the email they get. Left out or nil, the email gives no reason.
- `api_key` (`String`): Overrides the client API key for this call only.

**Returns**

A Hash with `status` `declined`, `endedBy` `host` and `endReason` holding the reason, or nil.

**Example**

```ruby
booking = client.bookings.decline(
  "bkg_2b8d4f6a1c3e5079b6d8f0a2",
  reason: "I am away that week. Please pick a time after the 20th."
)

puts booking[:status], booking[:endReason]
```

**Notes**

- A booking that is not waiting for approval answers 409 `booking_not_pending`. To call off a confirmed meeting, use `cancel`. A missing booking is a 404 `booking_not_found`.
- A `reason` over 500 characters is 422 `invalid_parameter`, and a key the body does not take is 422 `unknown_parameter`.
- The booking is declined even when the email cannot be sent. `guestMailFailed` is then true, and `resend_email` sends it again.
- An API key acts as the workspace owner and reaches the bookings of the owner, and a connected app reaches the bookings of the person who connected it.
- A key or an app limited to particular addresses or domains is refused with 422 `capability_unsupported`, because a booking page reads the whole calendar of its person.
- The SDK does not retry it, because a retry could email the guest twice. A 409 `booking_not_pending` on your own second attempt after a lost response means the first one worked or somebody else answered, and `get` says which.

Also available in: API [`POST /bookings/{id}/decline`](https://openemail.uk/docs/api/reference/booking-pages#post-bookings-id-decline); TypeScript [`bookings.decline()`](https://openemail.uk/docs/sdk/reference/bookings#decline); Python [`bookings.decline()`](https://openemail.uk/docs/python/reference/bookings#decline); PHP [`bookings->decline`](https://openemail.uk/docs/php/reference/bookings#decline); Go [`Bookings.Decline`](https://openemail.uk/docs/go/reference/bookings#decline); Java [`bookings().decline`](https://openemail.uk/docs/java/reference/bookings#decline); C# [`Bookings.DeclineAsync`](https://openemail.uk/docs/csharp/reference/bookings#decline); CLI [`openemail bookings decline`](https://openemail.uk/docs/cli/reference/bookings#bookings-decline).

### `bookings.cancel`

Cancel a booked meeting

```ruby
cancel(id, body = nil, api_key: nil, **fields) -> Hash
```

Cancels a meeting that has not ended yet and cancels its calendar event. The guest is told by email, sent from the address of the page with the cancellation attached, and with `reason` in it when one is given. Call it with the id alone to cancel without a reason.

A booking that still waits for approval is declined instead, so it ends as `declined`, not `cancelled`. The email goes out as `config.fromEmail`, so the call needs `emails:send` beside `calendar:write`.

Scopes: `calendar:write`, `emails:send`.

**Parameters**

- `id` (`String`, required): Booking id such as `bkg_2b8d4f6a1c3e5079b6d8f0a2`, as `list` returns it.
- `reason` (`String or nil`): A sentence for the guest, trimmed, at most 500 characters, included in the email they get. Left out or nil, the email gives no reason.
- `api_key` (`String`): Overrides the client API key for this call only.

**Returns**

A Hash with `status` `cancelled`, or `declined` when it still waited for approval, `endedBy` `host` and `endReason` holding the reason, or nil.

**Example**

```ruby
booking = client.bookings.cancel(
  "bkg_2b8d4f6a1c3e5079b6d8f0a2",
  reason: "Something urgent came up. Please book another time."
)

puts booking[:status], booking[:endedBy], booking[:endReason]
```

**Notes**

- A booking that was already declined or cancelled, or whose meeting is over, answers 409 `booking_ended`. A missing one is a 404 `booking_not_found`.
- There is no undo. The time is free again and the guest has to book once more.
- A `reason` over 500 characters is 422 `invalid_parameter`, and a key the body does not take is 422 `unknown_parameter`.
- The booking is cancelled even when the email cannot be sent. `guestMailFailed` is then true, and `resend_email` sends it again.
- An API key acts as the workspace owner and reaches the bookings of the owner, and a connected app reaches the bookings of the person who connected it.
- A key or an app limited to particular addresses or domains is refused with 422 `capability_unsupported`, because a booking page reads the whole calendar of its person.
- The SDK does not retry it, because a retry could email the guest twice. A 409 `booking_ended` on your own second attempt after a lost response means the first one worked or the guest cancelled, and `get` says which.

Also available in: API [`POST /bookings/{id}/cancel`](https://openemail.uk/docs/api/reference/booking-pages#post-bookings-id-cancel); TypeScript [`bookings.cancel()`](https://openemail.uk/docs/sdk/reference/bookings#cancel); Python [`bookings.cancel()`](https://openemail.uk/docs/python/reference/bookings#cancel); PHP [`bookings->cancel`](https://openemail.uk/docs/php/reference/bookings#cancel); Go [`Bookings.Cancel`](https://openemail.uk/docs/go/reference/bookings#cancel); Java [`bookings().cancel`](https://openemail.uk/docs/java/reference/bookings#cancel); C# [`Bookings.CancelAsync`](https://openemail.uk/docs/csharp/reference/bookings#cancel); CLI [`openemail bookings cancel`](https://openemail.uk/docs/cli/reference/bookings#bookings-cancel).

### `bookings.resend_email`

Send the guest the email about their booking again

```ruby
resend_email(id, api_key: nil) -> Hash
```

Sends the guest the email that matches where the booking stands now: the request while it waits for approval, the confirmation with its invitation once it is confirmed, or the notice that it was declined or cancelled, with the reason that was given. Use it when `guestMailFailed` is true. It takes no body and changes nothing else about the booking.

Scopes: `calendar:write`, `emails:send`.

**Parameters**

- `id` (`String`, required): Booking id such as `bkg_2b8d4f6a1c3e5079b6d8f0a2`, as `list` returns it.
- `api_key` (`String`): Overrides the client API key for this call only.

**Returns**

A Hash with `guestMailFailed` as it is after the send: false when the email went out, true when it failed again.

**Example**

```ruby
booking = client.bookings.resend_email("bkg_2b8d4f6a1c3e5079b6d8f0a2")

puts "Still not sent to #{booking[:guest][:email]}" if booking[:guestMailFailed]
```

**Notes**

- A missing booking is a 404 `booking_not_found`.
- It answers 200 whether or not the email went out, so read `guestMailFailed` to know.
- An API key acts as the workspace owner and reaches the bookings of the owner, and a connected app reaches the bookings of the person who connected it.
- A key or an app limited to particular addresses or domains is refused with 422 `capability_unsupported`, because a booking page reads the whole calendar of its person.
- Not retried automatically: every call sends another email, so a retry after a lost response can reach the guest twice.

Also available in: API [`POST /bookings/{id}/resend`](https://openemail.uk/docs/api/reference/booking-pages#post-bookings-id-resend); TypeScript [`bookings.resendEmail()`](https://openemail.uk/docs/sdk/reference/bookings#resendEmail); Python [`bookings.resend_email()`](https://openemail.uk/docs/python/reference/bookings#resendEmail); PHP [`bookings->resendEmail`](https://openemail.uk/docs/php/reference/bookings#resendEmail); Go [`Bookings.ResendEmail`](https://openemail.uk/docs/go/reference/bookings#resendEmail); Java [`bookings().resendEmail`](https://openemail.uk/docs/java/reference/bookings#resendEmail); C# [`Bookings.ResendEmailAsync`](https://openemail.uk/docs/csharp/reference/bookings#resendEmail); CLI [`openemail bookings resend-email`](https://openemail.uk/docs/cli/reference/bookings#bookings-resend-email).