ClockIn/ClockOut
Payloads
Each event will consist of
| Payload Field | Description |
|---|---|
payload.event | The category of the event (clockin, clockout) |
payload.data.id | The unique identifier for the timesheet. |
payload.data.operation | The action performed on the resource (clockin_created, clockout_updated) |
payload.data.last_updated_at | Unix timestamp indicating when the event occurred |
Example Payloads
Clock In
Fired when a user punches in. Timesheet row was just created, end is still null.
{
"payload": {
"event": "clockin",
"data": {
"id": 4821993,
"operation": "clockin_created",
"last_updated_at": 1756209841
}
}
}Clock Out
Fired when a user punches out. Same timesheet row as the matching clock in — id is identical, now updated with an end time.
{
"payload": {
"event": "clockout",
"data": {
"id": 4821993,
"operation": "clockout_updated",
"last_updated_at": 1756238104
}
}
}Get Timesheet Details
After receiving a webhook event for a timesheet, you can retrieve the full timesheet details using the Timesheet API endpoint. Use the payload.data.id provided in the payload to fetch the latest state of the timesheet.
Updated 23 days ago
Did this page help you?