Submits draft time entries for approval.

POST /psa/time-entries/submit

Group: PSA › Time Entries · Operation ID: submitTimeEntries

Submits time entries for approval, setting their status to pending and stamping submissionDate. The lifecycle is draft, then pending, then approved, then invoiced, with rejected branching off pending. Only an entry that has not been through approval can be submitted: one that is draft, or rejected so a corrected entry can be sent again. An entry that is already pending, approved or invoiced fails with ENTRY_STATUS_INVALID, which reports each entry's current status, and nothing is submitted. Resubmitting does not undo an approval: an approved entry is never returned to pending. To change an approved entry, correct it with PATCH psa/time-entries, which resets its approval and returns it to draft. The request fails if the id list is empty, and fails with NOT_FOUND if any id matches no time entry.

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: submitTimeEntriesInput.

Field	Type	Required	Description
`ids`	array of string	yes	The unique identifiers of the time entries to submit for approval.

Example:

{
  "ids": [
    "9b1c7f42-3d8a-4e05-b6c1-27fa5e903d18"
  ]
}

Response

200 Success

Under data (submitTimeEntriesOutput):

Field	Type	Required	Description
`submitted`	array of object	yes	The entries whose status was set to pending.
`submitted[].id`	string	yes	The unique identifier for the entry.

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_STATUS_INVALID`	400
`IDEMPOTENCY_KEY_CONFLICT`	409
`IDEMPOTENCY_PAYLOAD_MISMATCH`	422

Statuses

400 — Invalid request or business failure. Codes: NOT_FOUND, ENTRY_STATUS_INVALID
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