Time Entries

Update time entry

Replace a time entry's start, end, and description. Setting endTime closes a running entry and fills in its duration.

put/time-entry/{id}

Path parameters

idstring required

Request body

startTimestring date-time required

endTimestring date-time

descriptionstring

Example request

{
  "startTime": "2026-01-31T09:00:00Z",
  "endTime": "2026-01-31T09:00:00Z"
}

Response

The updated time entry

idstring required

taskIdstring required

userIdstring nullable required

Null once the user who logged the time has been removed.

descriptionstring nullable required

startTimestring date-time required

endTimestring date-time nullable required

Null while the timer is still running.

durationnumber nullable required

Elapsed seconds, filled in once the entry has an endTime.

createdAtstring date-time required

updatedAtstring date-time required

Changes

Changed in 8 of the 23 revisions of this API.1821

Aug 24, 202608bbb5bedb5d34See the full diff
- ▲
  the endTime request property type/format changed from string/ to string/date-time
  request-property-type-changed
- ▲
  the startTime request property type/format changed from string/ to string/date-time
  request-property-type-changed
- ▲
  the response property endTime became nullable for the status 200
  response-property-became-nullable
- ○
  added the non-success response with the status 400
  response-non-success-status-added
- ○
  added the non-success response with the status 401
  response-non-success-status-added
- ○
  added the non-success response with the status 403
  response-non-success-status-added
- ○
  the response property endTime became required for the status 200
  response-property-became-required
This revision also has 3 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Jul 11, 202632cece1ebe4341See the full diff
- ▲
  request body became required
  request-body-became-required
- ▲
  the createdAt response's property type/format changed from / to string/date-time for status 200
  response-property-type-changed
- ▲
  the endTime response's property type/format changed from / to string/date-time for status 200
  response-property-type-changed
- ▲
  the startTime response's property type/format changed from / to string/date-time for status 200
  response-property-type-changed
- ○
  added the required property updatedAt to the response with the 200 status
  response-required-property-added
Mar 5, 2026c45ef22a736c33See the full diff
- ▲
  the response property description became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property duration became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property userId became nullable for the status 200
  response-property-became-nullable
- ○
  response property description list-of-types was narrowed by removing types null from media type application/json of response 200
  response-property-list-of-types-narrowed
- ○
  response property duration list-of-types was narrowed by removing types null from media type application/json of response 200
  response-property-list-of-types-narrowed
- ○
  response property userId list-of-types was narrowed by removing types null from media type application/json of response 200
  response-property-list-of-types-narrowed
Mar 4, 2026298877d6a79a3See the full diff
- ▲
  response property description list-of-types was widened by adding types null to media type application/json of response 200
  response-property-list-of-types-widened
- ▲
  response property duration list-of-types was widened by adding types null to media type application/json of response 200
  response-property-list-of-types-widened
- ▲
  response property userId list-of-types was widened by adding types null to media type application/json of response 200
  response-property-list-of-types-widened
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Feb 21, 20264b8811b821e633See the full diff
- ▲
  the response property description became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property duration became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property userId became nullable for the status 200
  response-property-became-nullable
- ○
  response property description list-of-types was narrowed by removing types null from media type application/json of response 200
  response-property-list-of-types-narrowed
- ○
  response property duration list-of-types was narrowed by removing types null from media type application/json of response 200
  response-property-list-of-types-narrowed
- ○
  response property userId list-of-types was narrowed by removing types null from media type application/json of response 200
  response-property-list-of-types-narrowed
Jan 11, 2026f6c7baa3692411See the full diff
- ▲
  the response property endTime became optional for the status 200
  response-property-became-optional
- ○
  removed subschema #1 subschema #2 from the endTime response property anyOf list for the response status 200
  response-property-any-of-removed
Dec 13, 202575119d670ebb1See the full diff
- ○
  added the new optional request property description
  new-optional-request-property
Dec 11, 202593b23177312618See the full diff
- ▲
  the response's body type/format changed from / to object/ for status 200
  response-body-type-changed
- ○
  added the required property createdAt to the response with the 200 status
  response-required-property-added
- ○
  added the required property description to the response with the 200 status
  response-required-property-added
- ○
  added the required property duration to the response with the 200 status
  response-required-property-added
- ○
  added the required property endTime to the response with the 200 status
  response-required-property-added
- ○
  added the required property id to the response with the 200 status
  response-required-property-added
- ○
  added the required property startTime to the response with the 200 status
  response-required-property-added
- ○
  added the required property taskId to the response with the 200 status
  response-required-property-added
- ○
  added the required property userId to the response with the 200 status
  response-required-property-added

Full history