Updates the hours or notes of time entries.

PATCH /psa/time-entries

Group: PSA › Time Entries · Operation ID: updateTimeEntries

Corrects the hours or notes of existing time entries and changes nothing else. Only the fields you supply for an entry change, and an omitted field is left as it was. If any id matches no time entry, the request fails with NOT_FOUND and nothing is changed.

Hours and notes are the only fields you can change. A time entry is identified by who logged the time, when, and against what, so to move time to another date, member or activity you delete the entry and create a new one. The status is not settable here either: it moves through POST psa/time-entries/submit, approve and reject.

Both hours and notes are content an approver signed off on, so correcting an approved entry resets its approval and returns it to draft, and it must be submitted and approved again.

If any target entry has been invoiced, the request fails with ENTRY_INVOICED and nothing is changed. An entry counts as invoiced by its status or by a non-null invoiced-hours value, so an entry part-way through invoicing is rejected too. A correction also enforces the project's time rules (required notes, no time on weekends or holidays, and per-member limits on hours per day, week and month) and checks that the team is active. These failures are reported as generic errors, not as named diagnostics.

Open in the interactive reference

Parameters

Name	In	Type	Required	Description
`Api-Version`	header	`"v1"`	yes	The API version this request targets, named by its public identifier. Required on every request; omitting it, or naming a version this company does not have, is answered with 400. This document describes version `v1`.
`Idempotency-Key`	header	string	no	An opaque caller-chosen string (1-255 characters) that makes this request safe to retry. Repeating the same key with an identical request body replays the original response instead of re-executing - but only once that original request succeeded; a failed attempt re-executes on retry. Repeating the key with a different body is answered with 422. A key still in flight is answered with 409 - as is a key whose original request was interrupted before it finished, for a few minutes afterwards, until that attempt is presumed dead. A completed response stays replayable for 24 hours. The key is scoped to the caller, not to the action: reusing it for a different action is answered with 409 or 422 rather than treated independently. On read actions this header is ignored. On write actions that cannot offer the guarantee it is answered with `400 IDEMPOTENCY_NOT_SUPPORTED` rather than silently ignored.

Request body

Required, application/json: updateTimeEntriesInput.

Field	Type	Required	Description
`timeEntries`	array of object	yes	The time entries to update.
`timeEntries[].id`	string	yes	The unique identifier of the time entry to update.
`timeEntries[].hours`	string (decimal)	no	New total hours for the entry. Omit to leave it unchanged.
`timeEntries[].notes`	string	no	New free-form notes. Omit to leave them unchanged, or pass an empty string to clear them.

Example:

{
  "timeEntries": [
    {
      "id": "9b1c7f42-3d8a-4e05-b6c1-27fa5e903d18",
      "hours": "7.5"
    }
  ]
}

Response

200 Success

Response headers

Idempotency-Replayed — Present and true only when this response replays a previously stored one for the same Idempotency-Key, rather than reflecting a live execution. Absent on a live response - never sent as false.

Errors

Code	Status
`NOT_FOUND`	400
`ENTRY_INVOICED`	400
`IDEMPOTENCY_KEY_CONFLICT`	409
`IDEMPOTENCY_PAYLOAD_MISMATCH`	422

Statuses

400 — Invalid request or business failure. Codes: NOT_FOUND, ENTRY_INVOICED
401 — Missing or invalid access token
403 — Not authorized
404 — Not found
409 — The Idempotency-Key is still being processed by another request.
422 — The Idempotency-Key was already used with a different request payload.
429 — Too many requests
500 — Internal server error