---
title: "List the guests on an order"
method: GET
path: "/shop/orders/{orderId}/guests"
tags: ["Orders"]
---

# List the guests on an order

`GET /shop/orders/{orderId}/guests`

Retrieve every guest attached to an order. The lead booker is the guest
with `is_lead_booker` set to `true` — there is at most one lead booker
per order.

## Response `200`

The guests on the order were successfully retrieved.

- object
  - `data` Guest[], required
    - `id` string, object-id, required — Stable identifier for the guest slot on an order. Used to attach intake-form answers, check the guest in or out, and link the slot to a `Customer` once one is resolved.
    - `checked_in_at` string, date-time, nullable, required — ISO-8601 timestamp at which the guest checked in for their visit. `null` until check-in happens.
    - `checked_out_at` string, date-time, nullable, required — ISO-8601 timestamp at which the guest checked out / finished their visit. `null` while the visit is still in progress.
    - `customer_id` string, uuid, nullable, required — The `Customer` the guest slot has been linked to, if any. `null` for walk-ins or anonymous guests that haven't been matched to a customer record yet.
    - `email` string, email, nullable — Email address captured for this guest, used to send the pre-visit intake form and post-visit follow-ups. `null` when no email has been supplied for the slot.
    - `first_name` string, required — The first name of the guest.
    - `intake_form_submission_id` string, object-id — Identifier of the most recent intake-form submission for this guest, if one exists. Use this to fetch the submitted answers from the guest-intake API.
    - `intake_form_complete` boolean, required — Whether the intake form for the guest is complete.
    - `is_lead_booker` boolean, required — Whether the guest is the lead booker.
    - `last_name` string, required — The last name of the guest.
    - `name` string, required — Full display name for the guest — typically `first_name` plus `last_name`, but kept as a separate field so the platform can render it consistently across receipts, intake forms and check-in screens.

## Other responses

- `404` — The resource couldn't be found

---

[API](https://skmtc.dev/try/apis/trybe-api.md) · [All operations](https://skmtc.dev/try/apis/trybe-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/try/trybe-api/revisions/f37f92702da5/schema)