Update Clock Entry

patch

https://{companyDomain}.bamboohr.com/api/v1/time-tracking/clock-entries/{id}

Partially updates a time tracking clock entry identified by its ID. Only the fields present in the body are changed. When start or timezone change, the entry's date and timesheetId are recomputed server-side and the entry is moved to the matching timesheet. When start, end or timezone is in the body, the resulting start and end (the body merged with the stored values) must fall on the same calendar day in the resulting timezone; an update that would make the entry cross local midnight, including one ending at exactly 00:00 the next day, is rejected with 422. Submit one entry per day instead. A body that changes none of those three fields is not re-validated against the stored times. Pass null for clockInLocation / clockOutLocation to clear the stored geolocation.

OAuth Scopes: time_tracking:timesheets.write

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

integer

required

The clock entry ID.

Body Params

Request body for a partial update of a clock entry. All fields optional; at least one required.

start

date-time

Updated clock-in timestamp (ISO 8601).

end

Updated clock-out timestamp (ISO 8601). Null while the entry is open. Combined with the stored or updated start and timezone, it must fall on the same calendar day as start; an end of exactly 00:00 the next day is rejected.

timezone

string

Updated IANA timezone identifier.

note

Updated free-text note.

projectId

Updated project association. Null to clear.

taskId

Updated task association. Null to clear.

clockInLocation

Updated geolocation captured at clock-in. Send null to clear.

clockOutLocation

Updated geolocation captured at clock-out. Send null to clear.

Responses

Language

Credentials

URL

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200The updated clock entry.

400Malformed request body.

401Unauthorized. Missing or invalid authentication.

403Forbidden. Insufficient permissions.

404Clock entry not found.

409Conflict. The parent timesheet is already approved, the entry overlaps another, or the timesheet does not accept clock entries.

422Validation error (e.g., invalid time range, the resulting start and end falling on different calendar days in the resulting timezone, invalid timezone, accuracy greater than 10000, or a missing updatable field).