---
title: "Update a time-entry by id"
method: PUT
path: "/api/v3/timeentries/{timeEntryId}"
tags: ["TimeEntries"]
---

# Update a time-entry by id

`PUT /api/v3/timeentries/{timeEntryId}`

Update fields of a single time-entry identified by its unique id.

The "id" field must be sent and correspond to an existing time-entry. 

Read more about the [time-entry object](/api-reference/legacy/timmi-timesheet/time-entries/time-entry) and any validation error that you might encounter when using this API.

There are different ways to update time-entries. Please see [this guide](/api-reference/legacy/timmi-timesheet/guides/update-time-entries) on how to update `time-entries` the right way depending on your use case.

## Request body

- TimeEntry — 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".

## Response `200`

OK

- object
  - `data` TimeEntry — 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".

## Other responses

- `400` — Problem
- `401` — Problem
- `403` — Problem
- `404` — Problem
- `500` — Problem

---

[API](https://skmtc.net/luccasoftware/apis/lucca-expenses.md) · [All operations](https://skmtc.net/luccasoftware/apis/lucca-expenses/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/luccasoftware/lucca-expenses/revisions/110f9897756c/schema)