The time entry object
View as MarkdownWhat every time entry looks like in responses: timer, entries and corrections.
idstring · uuid- The entry's ID.
user_idstring · uuid- Whose time it is.
statusstring- Timer state.Allowed:
runningpausedstopped started_atstring · date-time- Start, ISO 8601.
ended_atstring · date-time- End, ISO 8601; null while running.
secondsinteger- Active seconds (paused time not counted).
hoursnumber- Active hours, two decimals.
descriptionstring- What the work was. Empty string when none.
billableboolean- Marked billable. Billable time counts only once a manager approves it.
approvedboolean- Approved by a manager or accountant.
task_idstring · uuid- The task the time is filed under; null when none.
taskstring- The task's name; null when none.
project_idstring · uuid- The project; null when none.
projectstring- The project's name; null when none.
clientstring- The project's client; null when none.
sourcestring- Where the entry came from: api, mobile_web (browser timer), desktop, kiosk, manual…
Billable and approval
Billable time counts as billable only once a manager or accountant approves it. Until then, reports show it as awaiting_approval_billable_hours and never price it. Approved time can't be changed with a personal key; time in a pay run can't be changed with any key.