Time entries
Read worked time and server-calculated totals for accounting and payroll.
Read punches and server-calculated minute totals for one employee in a date range. This is the public API for accounting and payroll systems.
Do not recalculate overtime, holidays or pay codes in your integration. Use the minutes on the response. Set rules and codes in Curio Time Web.
GET https://pro.curiotime.com/api/v1/companies/{companyId}/time-entries?employeeId={employeeId}&startDate={yyyy-MM-dd}&endDate={yyyy-MM-dd}
Authorization: Bearer {token}
| Query | Required | Description |
|---|---|---|
employeeId |
Yes | Employee GUID (also present on each entry and assigned shift) |
startDate |
Yes | Inclusive start (yyyy-MM-dd) |
endDate |
Yes | Inclusive end (yyyy-MM-dd) |
Roles: employee (own), manager, owner, accountant
For payroll and bookkeeping, use entries where isDraft is false and isLocked is true.
Response shape
{
"success": true,
"data": {
"entries": [
{
"id": "…",
"employeeId": "…",
"userId": "…",
"startAtUtc": "2026-08-25T08:00:00Z",
"endAtUtc": "2026-08-25T16:30:00Z",
"localCalendarDateYmd": "2026-08-25",
"isDraft": false,
"isLocked": true,
"projectId": "…",
"daytimeMinutes": 480,
"overtimeMinutes": 30,
"nightTimeMinutes": 0,
"weekendMinutes": 0
}
],
"totals": {
"totalMinutes": 510,
"daytimeMinutes": 480,
"overtimeMinutes": 30
}
},
"errors": null
}
Key fields
entries[]
| Field | Description |
|---|---|
employeeId |
Canonical employee GUID |
userId |
Deprecated compatibility alias; currently the same value as employeeId |
startAtUtc / endAtUtc |
Punch interval (UTC). endAtUtc null = open punch |
isDraft |
Draft — skip for payroll |
isLocked |
Approved / locked for payroll |
daytimeMinutes, overtimeMinutes, … |
Per-entry buckets (0 if the punch is still open) |
totals
Minute buckets for the requested range, already calculated on the server. Paid absence minutes in the period may appear here (for example sick or vacation minutes). They are results, not a holiday or pay-code API.
This resource is read-only. Only operations documented on this site and in the published OpenAPI specification are supported.
Related
- Schedules — planned shift vs worked time