---
title: "Get Drop-in Reservations"
method: GET
path: "/classes/reservations/drop-ins"
tags: ["Class Reservations"]
---

# Get Drop-in Reservations

`GET /classes/reservations/drop-ins`

Returns a list of Drop-in Class Reservations.

## Query parameters

- `sort` string
- `page` integer
- `page_size` integer

## Headers

- `x-api-key` string, required

## Response `200`

List of Drop-in Class Reservations

- ResponseDropInClassReservations — Drop-in Class Reservations
  - `drop_in_class_reservations` DropInClassReservationResponse[] — List of Drop-in Class Reserervations
    - `reservation_id` integer — Reservation&#39;s Id
    - `drop_in_name` string — Name of the Drop In
    - `drop_in_email` string — Email of the Drop In
    - `class_id` integer — Reservation&#39;s Class Id (Identifier)
    - `class` string — Reservation&#39;s class name
    - `utc_class_start_datetime` string, date-time — Date Time that the Class Starts (UTC)
    - `utc_class_end_datetime` string, date-time — Date Time that the Class Ends (UTC)
    - `local_class_start_datetime` string, date-time — Date Time that the Class Starts (Local)
    - `local_class_end_datetime` string, date-time — Date Time that the Class Ends (Local)
    - `program_id` string — Resrvation&#39;s Program Id (Identifier)
    - `program` string — Reservation&#39;s Program Name
    - `location_id` integer — Reservations Location Id (Identifier)
    - `location_name` string — Reservation&#39;s Location Name
    - `coaches` CoachResponse[] — List of Coaches assigned to the class
      - `coach_id` integer — User Id (Identifier) of the coach
      - `coach` string — Name of the coach
      - `payroll_position_id` integer — Payroll position Id of the coach
      - `payroll_position` string — Name of the payroll position the coach is assigned to for the class
    - `reservation_status_id` integer — Reservation Status Id (Identifier)
    - `reservation_status` string — Reservation Status
    - `created` Created — Record creation data.
      - `created_by_id` integer — Unique ID of the user that created the record.
      - `created_by` string — Name of the user that created the record.
      - `created_on_datetime` string, date-time — Datetime on which the record was created.
    - `updated` Updated — Update info
      - `updated_by_id` integer — Unique ID of the user that last updated the record.
      - `updated_by` string — Name of the user that most recently updated the record.
      - `updated_on_datetime` string, date-time — Datetime on which the record was last updated.
    - `membership_id` integer — Id of the Membership used for the Reservation
    - `membership` string — Membership used for the Reservation
    - `is_cancelled_from_waitlist` boolean — Determines if the Reservation was cancelled from waitlist
    - `is_late_cancellation` boolean — Determines if the Reservation is a Late Cancellation
  - `pagination` Pagination — Pagination for API method responses.
    - `page` integer, required — Current page number.
    - `page_size` integer, required — Number of records per page.
    - `has_more` boolean, required — True if more records exist beyond the current page.
  - `wodify_validation_result` string — The purpose of this attribute is to save any UserException message, that is, and user friendly message that should be shown to the end user. All methods should have, just like service actions: - an UserException with Abort Transaction = Yes, and a Log Error = No - an AllExceptions with Abort Transaction = Yes, and a Log Error = Yes With this, any known issue that we don&#39;t consider an error log, like a business validation, we raise it to be catch in the UserException and we don&#39;t log it. Then, in the OnResponse of the full REST service, the Build_Response_JSON action will take care on the output json format. An Exception will have the default formatted error message. If its an AllException, it will log the error so that we can fix it. If its a UserException, it will deliver as an error but it won&#39;t log it as an error. A success output will not have this attribute, the Build_Response_JSON will remove it from the final output.

---

[API](https://skmtc.net/wodify/apis/leads.md) · [All operations](https://skmtc.net/wodify/apis/leads/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/wodify/leads/revisions/974500ca0714/schema)
