# [EXPERIMENTAL] Create Employee Unavailability Create an unavailability for an employee Endpoint: POST /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. ## 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. ## Request fields (application/json): - `from` (string, required) Example: "2021-01-01T06:00:00Z" - `to` (string, required) Example: "2021-01-10T06:00:00Z" - `description` (string) Example: "holiday" ## Response 201 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" ## 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