---
title: "Get Class Sign-ins"
method: GET
path: "/clients/{client_id}/classes/sign-ins"
tags: ["Class Sign-ins"]
---

# Get Class Sign-ins

`GET /clients/{client_id}/classes/sign-ins`

Get a list of Class Sign-ins for a Client.

## Path parameters

- `client_id` integer, required

## Query parameters

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

## Headers

- `x-api-key` string, required

## Response `200`

returns a paginated list of Class Sign-ins for the given Client

- ResponseClientClassSignIns — Client Class Sign-ins
  - `class_sign_ins` ClientClassSignIn[] — List of Client Class Sign-ins
    - `id` integer — Id of the Class Sign-in
    - `client_id` integer — Id of the Signed-in Client
    - `client` string — Name of the signed-in Client
    - `email` string — Email of the signed-in Lead
    - `gender_id` integer — Gender Id of the signed-in Lead
    - `gender` string — Gender of the signed-in Lead
    - `class_id` integer — Id of the Class that the Sign-in is for
    - `class` string — Name of the Class the Sign-in is for
    - `sign_in_date_time` string, date-time — Datetime of the sign-in
    - `sign_in_source_id` integer — Source Id of the sign-in
    - `sign_in_source` string — Source of the sign in
    - `utc_class_start_datetime` string, date-time — Date Time that the Class Starts (UTC)
    - `local_class_start_datetime` string, date-time — Date Time that the Class Starts (Local)
    - `utc_class_end_datetime` string, date-time — Date Time that the Class Ends (UTC)
    - `local_class_end_datetime` string, date-time — Date Time that the Class Ends (Local)
    - `program_id` integer — Program Id of the Class
    - `program` string — Program of the Class
    - `location_id` integer — Location Id of the Class
    - `location` string — Location of the Class
    - `membership_id` integer — Id of the Membership of the Lead that applies to the Class Sign-in
    - `membership` string — Membership of the Lead that applies to the Class Sign-in
    - `online_membership_sale_id` integer — Id of the OnlineSale related to the sign-in. Only applicable if a free trial/drop-in booked from the Online Sales Portal.
    - `is_drop_in` boolean — Indicates if the Class Sign-in was for a drop-in
    - `is_auto_sign_in` boolean — Indicates if the sign-in occurred automatically
    - `counts_towards_attendance_limits` boolean — Indicates if the sign-in counts towards the Memberships attendance limit
    - `is_membership_enforcement_enabled` boolean — Indicates if Membership enforcement is enabled at time of sign-in
    - `limited_plan_enforcement_type_id` integer — Id of the enforcement type for Limited Class Plans at the time of sign-in
    - `limited_plan_enforcement_type` string — Enforcement type for Limited Class Plans at the time of sign-in
    - `class_pack_enforcement_type_id` integer — Id of the enforcement type for Class Packs at the time of sign-in
    - `class_pack_enforcement_type` string — Enforcement type for Class Packs at the time of sign-in
    - `is_attended_email_sent` boolean — Indicates if the attended email was sent
    - `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.
  - `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't consider an error log, like a business validation, we raise it to be catch in the UserException and we don'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'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)