/api/v3/timeentries
: if you have precise requirements regarding
TimeEntries lifecycle (when a TimeEntry should be deleted, edit a very specific TimeEntry and not another ‘look-a-like’) to match
an existing business logic. [recommended]/timmi-timesheet/services/time-entries
: if you only want to
send “what Alexander given timesheet should look like”, without caring what might it already betimeSource
or a creationSource
depending on the endpoints used :
timeSource=manual
or creationSource=2
for standard TimeEntries that users should be able to edit normally. [the default for any TimeEntry]timeSource=import
or creationSource=3
for read-only TimeEntries that only users with “Edit times” right should be able to edit through the user interface. (only for attendance-schedule-clock-in/clock-out or activity-schedule timesheet modes)timeSource=timer
or creationSource=4
for clocked-in / clocked-out TimeEntries that users should be able to adjust if necessary. After editing the TimeEntry, timeSource
/creationSource
will be set to manual
/2
.{yourDomain}
, eg: “https://myawesomecompany.ilucca.net”.{apiKey}
that has editing rights on the TimeEntries of the users concerned by your integration project./api/v3/timeentries
POST, PUT, and DELETE endpoints.
/timmi-timesheet/services/time-entries
endpoint.