---
title: "Assign a schedule to an employee"
method: POST
path: "/companies/{company}/work-schedules/{schedule}/assign"
tags: ["Work Schedules"]
---

# Assign a schedule to an employee

`POST /companies/{company}/work-schedules/{schedule}/assign`

## Request

- Base URL: `https://api.factuarea.com/v1`
- URL: `https://api.factuarea.com/v1/companies/{company}/work-schedules/{schedule}/assign`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-API-Key`

Assign the work schedule to an employee with an effective start date; the previous open assignment is closed and history is kept.
- `employee_id` and `effective_from` (`Y-m-d`) are required.
- An unknown employee returns 422 `assigned_employee_not_found`; moving back the start of an assignment already in effect returns 422.
- Returns the created assignment.

## Path parameters

- `company` string, uuid, required
- `schedule` string, uuid, required

## Headers

- `Idempotency-Key` string
- `Factuarea-Version` string, date

## Request body

- AssignScheduleRequest
  - `employee_id` string, uuid, required: Employee ID (UUID v7) the schedule is assigned to.
  - `effective_from` string, date, required: Assignment effective start date, in `Y-m-d`.

## Response `201`

- object
  - `data` ScheduleAssignment, required: The effective-dated assignment of a work schedule to an employee. Assigning a schedule closes the employee’s previously open assignment and opens a new one, preserving history. `effective_to` is `null` while the assignment is still open.
    - `id` string, uuid, required: Opaque identifier of the assignment, a UUID v7.
    - `object` 'work_schedule_assignment', required: Always `work_schedule_assignment`.
    - `work_schedule_id` string, uuid, required: UUID v7 of the assigned work schedule.
    - `employee_id` string, uuid, required: UUID v7 of the assigned employee.
    - `effective_from` string, date, required: Date the assignment starts being effective, in `Y-m-d`.
    - `effective_to` string, date, nullable, required: Date the assignment stops being effective, in `Y-m-d`; `null` while open.
    - `created_at` string, date-time, nullable, required: Creation timestamp (ISO 8601).

## Other responses

- `400`: `parameter_unknown` with `subcode` `retired_active_profile_header`: the retired `X-Active-Profile` header was sent; the company goes in the path. `parameter_invalid_format` on `Factuarea-Version`: the header is not a `YYYY-MM-DD` date. `unsupported_api_version`: the `Factuarea-Version` date is not a supported version.
- `401`: Missing or invalid API key.
- `403`: The request is authenticated but not allowed: the API key lacks the required scope (`insufficient_scope`), the plan does not include the public API or this feature (`addon_not_active`, `feature_not_available_in_plan`), or the module is not available with a test key (`module_not_available_in_sandbox`).
- `404`: The requested resource does not exist or belongs to another company.
- `409`: The request conflicts with data that already exists or with a request running at the same time. `resource_conflict`: another request was reserving identifiers for the same kind of record at that moment and this one could not complete its reservation. Nothing was written; send the request again after a few seconds.
- `422`: Validation failed. The `error.param` field identifies which input is invalid.
- `429`: Rate limit exceeded. Retry after the duration in `Retry-After`.
- `500`: Unexpected server error.

---

[API](https://skmtc.dev/factuarea/apis/factuarea-public-api.md) · [All operations](https://skmtc.dev/factuarea/apis/factuarea-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/factuarea/apis/factuarea-public-api/revisions/718e77934422?raw)