Update a time-entry by id

Headers

Authorization

string

required

API key. Value must be formatted like so: lucca application={api_key}.

Path Parameters

timeEntryId

integer

required

Identifier of the time-entry.

Body

application/json

time-entries are the working time sequences spent by a user on any given day.

time-entries come in different units and submission modes that should match the timesheet configuration of a given owner on a given day.

About units & duration

Lucca Timesheet supports up to 3 different units when it comes to entering time-entries. These are:

0: Days In this case, the user does not enter the exact hours he/she started working, but rather the total duration spent as a fraction of a day. For example: "John worked half a day on Monday".
1: Hours In this case, the user still does not enter the exact hours, but only the duration spent in hours. For example: "John worked 7h30min yesterday".
2: Time In this unit, the user has to enter the actual time he/she started working, as well as the end time. For example: "John started working at 08:00 for 3 hours, thus ending at 11:00".

enum TimeEntryUnit:
{
    Days = 0,
    Hours = 1,
    Time = 2
}

Whichever the unit, the time-entry is mainly determined by three properties:

(int) ownerId: The user it belongs to.
(date-time) startsAt: The date and time when the user started working. In Days and Hours units, the time part can only be 00:00:00 for "morning" (AM) or 12:00:00 for the "afternoon" (PM).
(duration) duration: The total time spent by the user from the time he/she started. In all units, this property is serialized as a string compliant with the Timespan formating: d.hh:mm:ss where d is the number of days (can be omitted if equal to zero which is in most cases), hh the number of hours, mm the number of minutes, and ss the number of seconds.

Some examples :

// TIME UNIT
// Case: "John (id: 416) worked between 09:45 and 12:15 on January, 1st 2021."
var timeEntry = {
  "ownerId": 416,
  "startsAt": "2021-01-01 09:45:00",
  "duration: "02:30:00",
  "unit": 2
};

// HOURS UNIT
// Case: "John (id: 416) spent 4h45min working on January, 1st 2021 in the morning"
var timeEntry = {
  "ownerId": 416,
  "startsAt": "2021-01-01 00:00:00",
  "duration: "04:45:00",
  "unit": 1
}

// DAYS UNIT
// Case: "John (id: 416) worked on the afternoon of January, 1st 2021"
var timeEntry = {
  "ownerId": 416,
  "startsAt": "2021-01-01 12:00:00",
  "duration: "12:00:00",
  "unit": 0
}

About submission modes

There are 2 submission modes in Lucca Timesheet:

Attendance: the user is expected to enter the sequences of work without much detail.
Activities: the user is expected to enter the time spent on each task / project / whatever.

Therefore, time-entries in activities mode have a supplementary property: the set of task / project / cost center / ... the user worked on. These analytical items are called AxisSections. More info here.

The time-entry is NOT determined by the axisSection[] it is associated with as a user can change the axisSection[].

{
  "ownerId": 416,
  "startsAt": "2021-01-01 00:00:00",
  "duration: "04:45:00",
  "unit": 1,
  "axisSections": [
    {
      "name": "R&D",
      "axis": {
        "name": "Cost centers"
      }
    },
    {
      "name": "My awesome project",
      "axis": {
        "name": "Projects"
      }
    },
    {
      "name": "Testing",
      "axis": {
        "name": "Tasks"
      }
    }
  ]
}

About time types

Each time-entry can reference a time type via its timeTypeId property.

Time types are a configured working time classification. It is generally used as a way of discriminating different types of working hours regarding compensation:

Attendance
Travels
etc...

Time types can only be used on users that belong to a specific regulation (ie time and attendance policy) mode: timeTrackingMode: typed. Whenever it is not the case, the timeTypeId property should be left null.

Validation rules

Locked timeentries after timesheet submission

A time-entry cannot be modified if its startsAt date belongs to an already submitted or approved timesheet.

StartsAt and timezones

The startsAt date-time property must be considered a floating date-time. As such, no UTC offset should be sent when creating or editing a time-entry.

Max duration

A time-entry cannot have a duration longer than 24h00 (ie one full day).

Cut at midnight

A time-entry cannot overlap 2 different days (example startsAt = 18:00:00 and duration = 10:00:00). It should be two distinct time-entries cut at 00:00:00.

Mandatory axisSection on activity timesheets

A time-entry must have axisSection if the corresponding timesheet is in activity mode, and vice-versa.

Inactive axisSection

A time-entry cannot be modified if one of its axisSection is no longer active (active=false).

Incompatible axisSections

A time-entry cannot have nested axisSections that does not meet a correct parent-child tree structure.

Fields

ownerId

integer

required

Reference to the time-entry owner.

Required range: x >= 1

Example:

199

unit

enum<integer>

required

Unit in which the time-entry has been entered.

0: Days (eg "1/2 day")
1: Hours (eg "8h15min")
2: Time (eg "23:45:00")

Available options:

0,

1,

2

Example:

2

startsAt

string<date-time>

required

The timeEntry start date and time. Please do NOT send any offset/timezone information ("Z", "+01:00", etc...).

Example:

"2022-01-01T08:00:00"

duration

string<timespan>

default:00:00:00

required

Duration of the time-entry in the "c" format of a C# timespan In other words : d.hh:mm:ss. Max: "1.00:00:00" (ie 24 hours).

Example:

"03:45:00"

owner

Timesheet User · object

The owner of this time-entry.

Show child attributes

owner.id

integer

Unique identifier of this User.

Required range: x >= 1

owner.firstName

string

Given name.

owner.lastName

string

Family name

owner.mail

string<email>

Email address.

owner.legalEntityId

integer

Unique identifier of the legal establishment this user currently has a work contract with.

creationSource

enum<integer>

default:2

Attribute used to identify last modification source :

0: Automatic fallback on theoretical time-entries from workcycles.
1: Entered with Lucca Timesheet quick-fill tools.
2: Manually created or edited (default).
3: Imported from external sources. Is read-only on Lucca Timesheet user interfaces only if Timesheet regulation is in following modes : attendance schedule with clock-in clock-out, and activity schedule.
4: Entered with Lucca Timesheet clock-in clock-out tool.

Available options:

0,

1,

2,

3

axisSections

The AxisSection resource · object[] | null

Represent the activities that time-entry should be associated with. When not in activity mode, send an empty array, or do not serialize this property.

Show child attributes

axisSections.id

integer

Required range: x >= 1

comment

object

A comment to add additional information about the given time-entry. It will be visible on Lucca Timesheet user interface.

Show child attributes

comment.content

string

Comment content

timeTypeId

integer | null

Optional reference of a configured Time Type. To use only if the timesheet is set up to use Time Types. Null otherwise.

Response

data

The time-entry resource · object

time-entries are the working time sequences spent by a user on any given day.

time-entries come in different units and submission modes that should match the timesheet configuration of a given owner on a given day.

About units & duration

Lucca Timesheet supports up to 3 different units when it comes to entering time-entries. These are:

0: Days In this case, the user does not enter the exact hours he/she started working, but rather the total duration spent as a fraction of a day. For example: "John worked half a day on Monday".
1: Hours In this case, the user still does not enter the exact hours, but only the duration spent in hours. For example: "John worked 7h30min yesterday".
2: Time In this unit, the user has to enter the actual time he/she started working, as well as the end time. For example: "John started working at 08:00 for 3 hours, thus ending at 11:00".

enum TimeEntryUnit:
{
    Days = 0,
    Hours = 1,
    Time = 2
}

Whichever the unit, the time-entry is mainly determined by three properties:

(int) ownerId: The user it belongs to.
(date-time) startsAt: The date and time when the user started working. In Days and Hours units, the time part can only be 00:00:00 for "morning" (AM) or 12:00:00 for the "afternoon" (PM).
(duration) duration: The total time spent by the user from the time he/she started. In all units, this property is serialized as a string compliant with the Timespan formating: d.hh:mm:ss where d is the number of days (can be omitted if equal to zero which is in most cases), hh the number of hours, mm the number of minutes, and ss the number of seconds.

Some examples :

// TIME UNIT
// Case: "John (id: 416) worked between 09:45 and 12:15 on January, 1st 2021."
var timeEntry = {
  "ownerId": 416,
  "startsAt": "2021-01-01 09:45:00",
  "duration: "02:30:00",
  "unit": 2
};

// HOURS UNIT
// Case: "John (id: 416) spent 4h45min working on January, 1st 2021 in the morning"
var timeEntry = {
  "ownerId": 416,
  "startsAt": "2021-01-01 00:00:00",
  "duration: "04:45:00",
  "unit": 1
}

// DAYS UNIT
// Case: "John (id: 416) worked on the afternoon of January, 1st 2021"
var timeEntry = {
  "ownerId": 416,
  "startsAt": "2021-01-01 12:00:00",
  "duration: "12:00:00",
  "unit": 0
}

About submission modes

There are 2 submission modes in Lucca Timesheet:

Attendance: the user is expected to enter the sequences of work without much detail.
Activities: the user is expected to enter the time spent on each task / project / whatever.

The time-entry is NOT determined by the axisSection[] it is associated with as a user can change the axisSection[].

{
  "ownerId": 416,
  "startsAt": "2021-01-01 00:00:00",
  "duration: "04:45:00",
  "unit": 1,
  "axisSections": [
    {
      "name": "R&D",
      "axis": {
        "name": "Cost centers"
      }
    },
    {
      "name": "My awesome project",
      "axis": {
        "name": "Projects"
      }
    },
    {
      "name": "Testing",
      "axis": {
        "name": "Tasks"
      }
    }
  ]
}

About time types

Each time-entry can reference a time type via its timeTypeId property.

Time types are a configured working time classification. It is generally used as a way of discriminating different types of working hours regarding compensation:

Attendance
Travels
etc...

Validation rules

Locked timeentries after timesheet submission

A time-entry cannot be modified if its startsAt date belongs to an already submitted or approved timesheet.

StartsAt and timezones

The startsAt date-time property must be considered a floating date-time. As such, no UTC offset should be sent when creating or editing a time-entry.

Max duration

A time-entry cannot have a duration longer than 24h00 (ie one full day).

Cut at midnight

A time-entry cannot overlap 2 different days (example startsAt = 18:00:00 and duration = 10:00:00). It should be two distinct time-entries cut at 00:00:00.

Mandatory axisSection on activity timesheets

A time-entry must have axisSection if the corresponding timesheet is in activity mode, and vice-versa.

Inactive axisSection

A time-entry cannot be modified if one of its axisSection is no longer active (active=false).

Incompatible axisSections

A time-entry cannot have nested axisSections that does not meet a correct parent-child tree structure.

Fields

Show child attributes

data.ownerId

integer

required

Reference to the time-entry owner.

Required range: x >= 1

Example:

199

data.unit

enum<integer>

required

Unit in which the time-entry has been entered.

0: Days (eg "1/2 day")
1: Hours (eg "8h15min")
2: Time (eg "23:45:00")

Available options:

0,

1,

2

Example:

2

data.startsAt

string<date-time>

required

The timeEntry start date and time. Please do NOT send any offset/timezone information ("Z", "+01:00", etc...).

Example:

"2022-01-01T08:00:00"

data.duration

string<timespan>

default:00:00:00

required

Duration of the time-entry in the "c" format of a C# timespan In other words : d.hh:mm:ss. Max: "1.00:00:00" (ie 24 hours).

Example:

"03:45:00"

data.id

integer

Unique identifier for this object.

Required range: x >= 1

data.owner

Timesheet User · object

The owner of this time-entry.

Show child attributes

data.owner.id

integer

Unique identifier of this User.

Required range: x >= 1

data.owner.firstName

string

Given name.

data.owner.lastName

string

Family name

data.owner.mail

string<email>

Email address.

data.owner.legalEntityId

integer

Unique identifier of the legal establishment this user currently has a work contract with.

data.endsAt

string<date-time>

Automatically set as startsAs + duration when editing a timeentry.

Example:

"2022-01-01T11:45:00"

data.authorId

integer

Identifier of the user who initially created this time-entry.

Example:

199

data.createdAt

string<date-time>

Date and time when time-entry was first created. (Central European Time)

Example:

"2022-01-01T18:35:10"

data.modifierId

integer

The unique identifier of the user who last updated the time-entry.

data.modifiedAt

string<date-time>

Date and time when time-entry was last modified. (Central European Time). The time-entry is modified by any change made to the time-entry, including when corresponding timesheet is sent for approbation (status=1) and when the timesheet is completely approved (status=2).

Example:

"2022-01-01T18:42:14"

data.archivedAt

string<date-time>

Date and time when time-entry was deleted (Central European Time). When null, implies that the time-entry still has not been deleted (and maybe never will).

Example:

"2022-01-01T18:41:12"

data.creationSource

enum<integer>

default:2

Attribute used to identify last modification source :

0: Automatic fallback on theoretical time-entries from workcycles.
1: Entered with Lucca Timesheet quick-fill tools.
2: Manually created or edited (default).
3: Imported from external sources. Is read-only on Lucca Timesheet user interfaces only if Timesheet regulation is in following modes : attendance schedule with clock-in clock-out, and activity schedule.
4: Entered with Lucca Timesheet clock-in clock-out tool.

Available options:

0,

1,

2,

3

data.layer

integer

Used to store the original workcycle at the time of time-entry modification. In 99.999% of use cases, you will want the 0 : Actual time-entry.

0: Actual time-entry.
1: Theoretical workcycle.

data.axisSections

The AxisSection resource · object[] | null

Represent the activities that time-entry should be associated with. When not in activity mode, send an empty array, or do not serialize this property.

Show child attributes

data.axisSections.id

integer

Required range: x >= 1

data.axisSections.code

string

data.axisSections.name

string

data.axisSections.multilingualName

string

data.axisSections.description

string

data.axisSections.ownerId

integer

Required range: x >= 1

data.axisSections.startOn

string<date-time>

data.axisSections.endOn

string<date-time>

data.axisSections.active

boolean

data.axisSections.axisId

integer

data.axisSections.parentAxisSections

object[]

data.axisSections.childrenAxisSections

object[]

data.comment

object

A comment to add additional information about the given time-entry. It will be visible on Lucca Timesheet user interface.

Show child attributes

data.comment.id

integer

data.comment.content

string

Comment content

data.comment.authorId

integer

Identifier of the user who initially created this comment

data.comment.createdAt

string<date-time>

Date and time when the comment was first created. (Central European Time)

data.timeTypeId

integer | null

Optional reference of a configured Time Type. To use only if the timesheet is set up to use Time Types. Null otherwise.

data.timesheetId

integer

The reference to the timeshet this timeentry is associated with when the timesheet is at least sent for approval. Is null if the timesheet is still pending submission.

Documentation

Files

Organization Structure API

Core HR API

Expenses API

Invoices API

Absences API

Office API

Project API

Schedule API

Timesheet API

Mealvouchers API

Compensation API

Training API

Headers

Path Parameters

Body

About units & duration

About submission modes

About time types

Validation rules

Locked timeentries after timesheet submission

StartsAt and timezones

Max duration

Cut at midnight

Mandatory axisSection on activity timesheets

Inactive axisSection

Incompatible axisSections

Fields

Response

About units & duration

About submission modes

About time types

Validation rules

Locked timeentries after timesheet submission

StartsAt and timezones

Max duration

Cut at midnight

Mandatory axisSection on activity timesheets

Inactive axisSection

Incompatible axisSections

Fields