The Check-In object

Attributes

• check_in_id string optional

  Unique identifier for the check-in. Optional - auto-generated from member_id and timestamp pair if not provided.

• member_id string required

  Unique identifier of the member.

• facility_id string either/orProvide the facility identifier type configured for your integration: use facility_id for direct-link integrations, or linking_identifier for linking-identifier integrations. Do not send both; the API uses the identifier type configured for your partner account and ignores the other one. Learn more

  Unique identifier of the facility from Performance Hub.

• linking_identifier string either/orProvide the facility identifier type configured for your integration: use facility_id for direct-link integrations, or linking_identifier for linking-identifier integrations. Do not send both; the API uses the identifier type configured for your partner account and ignores the other one. Learn more

  Unique identifier value for each location that the partner uses (e.g., "Branch ID", "Location Code", "Store Number"). Learn more

• check_in_type string optional

  Type of visit. One of member, class, staff, guest, or trial.

• source string optional

  How the check-in was captured. Common values include manual, tag, rfid, kiosk, app. Additional values like door_reader or booking may also be used.

• class_id string optional

  Optional. If tied to a class booking or attendance.

• timestamp string required

  ISO 8601 format timestamp of when the check-in occurred.

The Check-In object

{
  // "check_in_id": "checkin_abc123",  // Optional - auto-generated from member_id + timestamp if not provided
  "member_id": "mem_12345",
  "facility_id": "550e8400-e29b-41d4-a716-446655440000",
  // "linking_identifier": "branch_downtown",  // If using linking identifier
  "check_in_type": "member",
  "source": "rfid",
  "timestamp": "2025-01-20T08:45:30Z"
}