Obtain an OAuth access token and appkey as described in the UKG Pro WFM authentication flow.
Prepare a punch import payload conforming to the UKG WFM punch import schema: each record includes employee identifier, punch type (in/out/break), timestamp, and optionally a work rule or labor account.
POST the punch records to the appropriate timekeeping import endpoint documented in the Developer Hub under the Timekeeping domain.
Check the response for individual record-level errors; UKG WFM may return partial success where some punches are accepted and others rejected with reason codes.
Resolve rejected records by correcting data issues (e.g., out-of-range timestamps, unknown employee IDs) and resubmit only the failed records.
Verify imported punches appear correctly in the timecard view before triggering any downstream payroll calculation steps.
Known gotchas
Punch timestamps must be submitted in the tenant's configured timezone or with explicit UTC offset; naive timestamps without timezone information may be misinterpreted.
Duplicate punch detection is handled server-side; submitting the same punch twice may create duplicate records rather than idempotently updating—track which punches have been successfully imported.
Some punch import endpoints require that the employee's timecard be in an editable state (not approved or locked); confirm timecard status before attempting imports.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp