# [EXPERIMENTAL] Get all Employee Unavailabilities by Employee business id

Get all Employee Unavailabilities by Employee business id. When a from and until are provided, we match any Unavailabilities that overlap with this range.

Endpoint: GET /employee/{business_id}/unavailability
Version: 1.27.2
Security: clientCredentials

## Path parameters:

  - `business_id` (string, required)
    A unique identifier of an entity instance. Should only contain characters which do not need URL encoding.

## Query parameters:

  - `from` (string)
    Example: "2021-01-01T10:15:30Z"

  - `until` (string)
    Example: "2021-01-05T10:15:30Z"

## Response 200 fields (application/json):

  - `id` (string)
    The unique Unavailability ID.
    Example: "f22896d0-ed42-4a14-a935-7a29072bc5ac"

  - `employee_id` (string)
    The unique Employee ID.

  - `from` (string, required)
    Example: "2021-01-01T06:00:00Z"

  - `to` (string, required)
    Example: "2021-01-10T06:00:00Z"

  - `description` (string)
    Example: "holiday"

  - `version` (integer)
    Version of the entity, can be used for optimistic locking.

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