---
title: "List Check-ins"
method: GET
path: "/customers/check-ins"
tags: ["CheckIns"]
---

# List Check-ins

`GET /customers/check-ins`

Retrieves a list of all check-ins, optionally filtered by customer, site, date range and method.

## Query parameters

- `customer_id` string[]
- `site_id` string
- `date_from` string
- `date_to` string
- `checked_in_at_from` string
- `checked_in_at_to` string
- `method_id` string
- `method_type` 'gantner'
- `page` integer
- `per_page` integer

## Response `200`

The check-ins were successfully retrieved

- object
  - `data` CheckIn[], required
    - `id` string, required — The ID of this check-in
    - `customer` CheckInCustomer, required — Summary details of the customer who checked in.
      - `id` string, uuid, required — The customer ID associated with this check-in
      - `first_name` string, required — The customer's first name
      - `last_name` string, required — The customer's last name
      - `full_name` string, required — The customer's full name
      - `email` string, required — The customer's email address
    - `membership_id` string, required — The membership ID associated with this check-in
    - `site_id` string, required — The site ID where this check-in happened
    - `method` CheckInMethod, required — Details of the method used to record the check-in.
      - `name` string, required — The name of the method used to create this check-in
    - `source` 'app' | 'kiosk' | 'gantner' | 'null', nullable, required — Where the check-in/out originated: `app` (staff app check-in button), `kiosk` (self-service kiosk), or `gantner` (Gantner access gate). Null for records created before source tracking existed.
    - `checked_in_at` string, date-time, nullable, required — The datetime when this check-in happened
    - `checked_out_at` string, date-time, nullable, required — The datetime when this check-out happened
  - `meta` PaginationMeta, required — Counts and positional information for the current page of a list response. Use `current_page` and `last_page` to drive pagination UI, `total` for result counts, and `per_page` to confirm the page size the server actually applied (which may differ from the requested value when capped).
    - `from` integer, required — The item number from which this results set starts from
    - `to` integer, required — The item number from which this results set ends at
    - `total` integer, required — The total number of results
    - `current_page` integer, required — The current page number
    - `last_page` integer, required — The page number of the last result set
    - `per_page` integer, required — The number of results per page
    - `path` string, required — The path of this api request
  - `links` PaginationLinks, required — Hypermedia navigation links for paging through a list response. Each property is a fully-qualified URL that preserves the original query string (filters, sort, page size) and only swaps the `page` parameter. `next` and `prev` are `null` at the ends of the result set; `first` and `last` are always present.
    - `first` string, required — The url of the first page for the paginated results set
    - `next` string, nullable, required — The url of the next page for the paginated results set
    - `prev` string, nullable, required — The url of the previous page for the paginated results set
    - `last` string, required — The url of the last page for the paginated results set

## Other responses

- `401` — The user is unauthenticated

---

[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)