---
title: "[DEPRECATED] Get Employee Punch Details"
method: GET
path: "/apiHub/time/v1/companies/{companyId}/employees/{employeeId}/punchDetails"
tags: ["Employee Punch Details"]
---

# \[DEPRECATED\] Get Employee Punch Details

`GET /apiHub/time/v1/companies/{companyId}/employees/{employeeId}/punchDetails`

## Request

- Base URL: `dc1demogwext.paylocity.com` (relative, and the document’s source URL is not known)
- URL: `dc1demogwext.paylocity.com/apiHub/time/v1/companies/{companyId}/employees/{employeeId}/punchDetails`
- Auth: HTTP bearer

**Summary Description**

The GET Punch Details API endpoint provides access to employee punch details effortlessly. The punch detail API will include all punch data for a single employee. It serves as a valuable tool for accessing, analyzing, and managing time-related records, providing intricate details related to employee punches. The Punch Details API can be filtered by date range

**The Paylocity Punch Detail use cases:**
- The Punch Detail API provides HR and payroll organizations with precise and comprehensive punch data for every employee. The provided data can be utilized to accurately compute employee salaries, incorporating overtime and rounding modifications
-  Organizations can employ the API to collect punch data for particular cost centers or departments. This enables comprehensive examination of labor efficiency, attendance, and time allocation. By having access to both rounded and precise punch times, firms can analyze patterns, evaluate employee punctuality, and utilize data-driven strategies to enhance operational efficiency
- The Punch Detail API is indispensable for ensuring adherence to labor standards. It offers a thorough record of employee punches, facilitating the demonstration of compliance during audits or inquiries. Users have the ability to apply filters based on date range, facilitating the retrieval of specific data needed for compliance reporting

## Path parameters

- `companyId` string, required
- `employeeId` string, required

## Query parameters

- `relativeStart` string, date-time, required
- `relativeEnd` string, date-time, required
- `testFlag` boolean

## Headers

- `Authorization` string, required

## Response `200`

Success

- PunchDetailRecordV1Model[]
  - `employeeId` string, nullable: The Paylocity Employee ID. This is a unique value per Paylocity Company ID.
  - `companyId` string, nullable: The Paylocity Company ID. This is the unique value provided by Paylocity to each specific Payroll Entity.
  - `badgeNumber` integer: The Time and Labor badge number
  - `relativeStart` string, date-time, nullable: The relative DateTime for the beginning of the WorkedShift
  - `relativeEnd` string, date-time, nullable: The relative DateTime for the end of the WorkedShift
  - `segments` WorkedShiftsSegmentV1Model[], nullable: Breakdown of the worked shift's durations by time card entry. The entire span of time from beginning of worked shift to end of worked shift is represented in this breakdown.
    - `punchID` string, uuid, nullable: A unique identifier assigned to each punch or time entry, ensuring that each entry is distinct, traceable, and easily referenced for tracking purposes.
    - `origin` string, nullable: The associated origin of the time entry.
    - `date` string, date: Date the worked shift segment took place. In the case of over night shifts, this is the date these worked hours apply to in payroll and can play a role in some overtime calculations.
    - `punchType` string, nullable: The type of punch recorded indicating whether it was recorded for categories such as work, lunch break etc
    - `relativeStart` string, date-time, nullable: Relative DateTime of the beginning of this segment after payroll policy rules are applied. Null if the segment began with a missed punch.
    - `relativeEnd` string, date-time, nullable: Relative DateTime of the end of this segment after payroll policy rules are applied. Null if the segment ended with a missed punch.
    - `relativeOriginalStart` string, date-time, nullable: Relative DateTimeOffset of the beginning of this segment before payroll policy rules are applied. Null if the segment began with a missed punch.
    - `relativeOriginalEnd` string, date-time, nullable: Relative DateTime of the end of this segment before payroll policy rules are applied. Null if the segment ended with a missed punch.
    - `durationSeconds` integer: The total seconds worked by the employee for a particular punch or time entry, reflecting the duration of their work.
    - `earnings` number, double: This field's use in the Paylocity product suite has been deprecated and will be removed in future versions of the API. It will always return 0.
    - `costCenters` CostCenterDto[], nullable: List of cost centers, at most one per cost center level, that this segment of the worked shift is allocated to.
      - `id` string, uuid: unique Guid
      - `costCenterId` integer: Cost center id
      - `level` integer: Cost center level
      - `code` string, nullable: Cost center code
      - `name` string, nullable: Cost center name
      - `isActive` boolean: The boolean value indicates whether the cost center is active or not.

## Other responses

- `400`: Bad Request
- `401`: Unauthorized
- `403`: Forbidden
- `429`: Too Many Requests
- `500`: Server Error

---

[API](https://skmtc.dev/paylocity/apis/punch-detail-api.md) - [All operations](https://skmtc.dev/paylocity/apis/punch-detail-api/llms.txt) - [OpenAPI document](https://skmtc.dev/paylocity/apis/punch-detail-api/revisions/7f0a1490bb93?raw)