Skip to main content
Developer Communities Admin
Community Manager
September 15, 2026

We currently have two available endpoints for employee punch creation:

  • September 15, 2026
  • 1 reply
  • 0 views

Originally posted by Hong Zhao on March 3, 2026 at 4:38 PM.

 

We currently have two available endpoints for employee punch creation:

  1. /{clientNamespace}/V1/EmployeeRawPunches. (Available since R56 SP3+)
  2. /{clientNamespace}/V1/EmployeePunches (Available since 2025.1.0)

 

Could someone clarify the functional differences between these two APIs and provide guidance on the specific use cases for each? Ideally, I'd like to know the criteria for choosing one over the other.

    1 reply

    Developer Communities Admin
    Community Manager
    September 15, 2026

    Originally replied by Frank Ruffolo on Mar 4, 2026, 10:04 AM.

     

    Hey @Hong Zhao​ EmployeePunches operates on employee time entry records (processed punches) while EmployeeRawPunch operates on raw clock entry records (unrounded, raw device times.)

     

    So:

    • Time entries (what EmployeePunches touches) = the processed/adjusted punches that drive pay and the normal timesheet.
    • Raw clock entries (what EmployeeRawPunch / Employee Raw Clock Entry touches) = the original device punches used for more detailed tracking and some rules.