# Get cursor-based actuals for an employee

Retrieve actuals for an employee in bulk using cursor-based paging (see the Cursor-based pagination documentation on the PTV Developer Portal).

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

## Path parameters:

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

## Query parameters:

  - `cursor` (string)
    The cursor of the page to return. No cursor is expected for the initial request. The cursors returned by this endpoint can be used for subsequent requests.

  - `limit` (integer)
    Number of results to return per page.

## Response 200 fields (application/json):

  - `data` (array)
    The set of results for the current page.

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

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

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

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

  - `data.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"

  - `data.etag` (string)
    Example: "W/\"25\""

  - `cursors` (object)
    The cursors represent pointers to pages of results in relation to the page that was retrieved by the current request. These pointers are nullable. For more information
on these pointers, view the Developer Portal.

  - `cursors.previous` (string)
    Pointer to the previous page of results.

  - `cursors.self` (string)
    Pointer to the current page of results. When changing the limit in subsequent requests, the first 'limit' results will be contained in the page.

  - `cursors.next` (string)
    Pointer to the next page of results.

## 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 401 fields