# [EXPERIMENTAL] Upsert Actual

Upsert a single Actual for an Employee.

Endpoint: PUT /means/{employee_id}/actual/{business_id}
Version: 1.27.2
Security: clientCredentials

## Path parameters:

  - `employee_id` (string, required)
    employee_id of the employee that the Actual applies to
    Example: "my-employee-id"

  - `business_id` (string, required)
    Unique identifier for this Actual. Should only contain characters which do not need URL encoding.

## Header parameters:

  - `Prefer` (array)
    The RFC7240 Prefer header indicates that a particular server behavior
is preferred by the client but is not required for successful completion
of the request (see RFC 7240).

The following behavior (see _Examples_) is supported by this API:
* return= is used to suggest the server to
  return using 204 without resource (minimal) or using 200 or 201 with
  resource (representation) in the response body on success.

  - `If-Match` (string)
    Weak Etag used for optimistic locking.
    Example: "W/\"24\""

## Request fields (application/json):

  - `start` (string, required)
    A date and time when the activity was started.
    Example: "2025-05-14T08:00:00Z"

  - `end` (string)
    A date and time when the activity has ended.
    Example: "2025-05-14T17:00:00Z"

  - `work_time` (string, required)
    The total work time performed by an Employee. Must be an ISO-8601 compliant Duration string. Must be strictly positive.
    Example: "PT8H"

## Response 201 fields (application/json):

  - `employee_id` (string, required)
    Example: "hvertenten"

  - `business_id` (string, required)
    Unique identifier for this Actual.
    Example: "14-05-2025-morning-shift"

  - `start` (string, required)
    A date and time when the activity was started.
    Example: "2025-05-14T08:00:00Z"

  - `end` (string)
    A date and time when the activity has ended.
    Example: "2025-05-14T17:00:00Z"

  - `work_time` (string, required)
    The total work time performed by an Employee. Must be an ISO-8601 compliant Duration string. Must be strictly positive.
    Example: "PT8H"

## Response 400 fields (application/problem+json):

  - `title` (string)
    A short, summary of the problem.
    Example: "Validation exception"

  - `detail` (string)
    A detailed explanation specific to this problem.
    Example: "The field contains invalid business formatting."

  - `violations` (array)

  - `violations.field` (string)
    Example: "path.to.field"

  - `violations.message` (string)
    Example: "Field is required"

## Response 404 fields (application/problem+json):

  - `title` (string)
    A short, summary of the problem.
    Example: "Validation exception"

  - `detail` (string)
    A detailed explanation specific to this problem.
    Example: "The field contains invalid business formatting."

## Response 412 fields (application/problem+json):

  - `title` (string)
    A short, summary of the problem.
    Example: "Validation exception"

  - `detail` (string)
    A detailed explanation specific to this problem.
    Example: "The field contains invalid business formatting."


## Response 204 fields

## Response 401 fields