# List personnel numbers

**Requires scope:** `employee_mappings`.
> **Legacy**, Kept for existing integrations. New integrations should use `GET /api/business/v3/employees`, which returns the same mapping (`employeeId` and `personnelNumber`) along with the full employee record.

Returns a list of personnel numbers and their corresponding Dyflexis employee ids. Employees that do not have a personnel number will be omitted.

Endpoint: GET /api2/employee-mappings
Security: apiKey

## Response 200 fields (application/json):

  - `employeeMappings` (array)

  - `employeeMappings.dyflexisId` (integer)
    The unique employee id used by Dyflexis
    Example: 1

  - `employeeMappings.personnelNumber` (string)
    The personnel number as known by the connecting party
    Example: 243-a

## Response 401 fields (application/json):

  - `title` (string, required)
    Short, human-readable summary of the error.
    Example: Unauthorized

  - `status` (integer, required)
    The HTTP status code.
    Example: 401

  - `message` (string, required)
    Human-readable explanation of this occurrence of the error.
    Example: Invalid Token

  - `detail` (string)
    Human-readable explanation of this occurrence. Not returned by all backend versions.
    Example: Invalid Token

  - `code` (integer)
    The HTTP status code (duplicate of `status`). Not returned by all backend versions.
    Example: 401

## Response 403 fields (application/json):

  - `title` (string, required)
    Short, human-readable summary of the error.
    Example: Unauthorized

  - `status` (integer, required)
    The HTTP status code.
    Example: 401

  - `message` (string, required)
    Human-readable explanation of this occurrence of the error.
    Example: Invalid Token

  - `detail` (string)
    Human-readable explanation of this occurrence. Not returned by all backend versions.
    Example: Invalid Token

  - `code` (integer)
    The HTTP status code (duplicate of `status`). Not returned by all backend versions.
    Example: 401