# Update Time Entry

Update an existing time entry. You can update the activity description, notes, task, project assignment, date, or time range. Requires workspace owner or executive manager permissions.

Important Notes:
- All fields except workspace_id are optional
- If you update only start_time or end_time, the other will be preserved from the existing entry
- Times are validated to ensure end_time is after start_time

Endpoint: PUT /time-entries/{time_entry_id}
Version: 2.0.0
Security: oauth2, apiKey

## Path parameters:

  - `time_entry_id` (string, required)
    Encrypted UUID identifier of the time entry to update
    Example: "a1b2c3d4-e5f6-7890-abcd-ef1234567890"

## Request fields (application/json):

  - `workspace_id` (integer, required)
    ID of the workspace
    Example: 1

  - `project_id` (integer,null)
    Project ID
    Example: 10

  - `task_id` (integer,null)
    Task ID
    Example: 5

  - `notes` (string,null)
    Activity notes or description
    Example: "Updated activity description"

  - `date` (string)
    Date of the time entry (format: Y-m-d)
    Example: "2026-01-29"

  - `start_time` (string)
    Start time in HH:mm format
    Example: "09:00"

  - `end_time` (string)
    End time in HH:mm format (must be after start_time)
    Example: "17:30"

## Response 200 fields (application/json):

  - `success` (boolean)
    Example: true

  - `message` (string)
    Example: "Time entry updated successfully"

  - `meta` (object)

  - `meta.api_version` (string)
    Example: "2.0.0"

  - `meta.timestamp` (string)
    Example: "2026-01-29T12:00:00.000000Z"

## Response 400 fields (application/json):

  - `success` (boolean, required)

  - `message` (string, required)
    Error message describing what went wrong
    Example: "An error occurred"

  - `error` (string,null)
    Optional additional error details
    Example: "Internal Server Error"

  - `meta` (object, required)

  - `meta.api_version` (string)
    Example: "2.0.0"

  - `meta.timestamp` (string)

## Response 401 fields (application/json):

  - `success` (boolean, required)

  - `message` (string, required)
    Error message describing what went wrong
    Example: "An error occurred"

  - `error` (string,null)
    Optional additional error details
    Example: "Internal Server Error"

  - `meta` (object, required)

  - `meta.api_version` (string)
    Example: "2.0.0"

  - `meta.timestamp` (string)

## Response 403 fields (application/json):

  - `success` (boolean, required)

  - `message` (string, required)
    Error message describing what went wrong
    Example: "An error occurred"

  - `error` (string,null)
    Optional additional error details
    Example: "Internal Server Error"

  - `meta` (object, required)

  - `meta.api_version` (string)
    Example: "2.0.0"

  - `meta.timestamp` (string)

## Response 404 fields (application/json):

  - `success` (boolean, required)

  - `message` (string, required)
    Error message describing what went wrong
    Example: "An error occurred"

  - `error` (string,null)
    Optional additional error details
    Example: "Internal Server Error"

  - `meta` (object, required)

  - `meta.api_version` (string)
    Example: "2.0.0"

  - `meta.timestamp` (string)

## Response 422 fields (application/json):

  - `success` (boolean)

  - `message` (string)
    Example: "Wrong time range"

  - `meta` (object)

  - `meta.api_version` (string)
    Example: "2.0.0"

  - `meta.timestamp` (string)
    Example: "2026-01-29T12:00:00.000000Z"

## Response 500 fields (application/json):

  - `success` (boolean, required)

  - `message` (string, required)
    Error message describing what went wrong
    Example: "An error occurred"

  - `error` (string,null)
    Optional additional error details
    Example: "Internal Server Error"

  - `meta` (object, required)

  - `meta.api_version` (string)
    Example: "2.0.0"

  - `meta.timestamp` (string)