---
title: "Unassign Employee Time Off Policy"
method: DELETE
path: "/api/v1/employees/{employeeId}/time-off/policies/{assignmentId}"
tags: ["Time Off", "Public API"]
---

# Unassign Employee Time Off Policy

`DELETE /api/v1/employees/{employeeId}/time-off/policies/{assignmentId}`

## Request

- Base URL: `https://companySubDomain.bamboohr.com`
- URL: `https://companySubDomain.bamboohr.com/api/v1/employees/{employeeId}/time-off/policies/{assignmentId}`
- Auth: one of:
  - HTTP basic
  - OAuth 2
    - Authorization code: `/authorize.php`
    - Token URL: `/token.php` scopes: `time_off:policies.write`
- TypeScript: <https://skmtc.dev/bamboohr/apis/bamboohr-api/docs/api/v1/employees/:employeeId/time-off/policies/:assignmentId/delete.ts> (a function with typed inputs; its response is checked against the schema)

Unassigns a time off policy from an employee. The assignment stops being current as of today; nothing is deleted, and the employee's historical balances and time off requests are preserved. Because the assignment is end-dated rather than removed, a subsequent `GET` of the employee's policies still returns it, under a new ID and carrying the past `endDate`. A future-dated assignment is unassigned as of its own effective date, and because it was never in force it leaves no historical record. Unassigning also ends any other assignment the employee holds in the same time off category that is scheduled to start after the unassignment date, so that they are not re-enrolled in that category later. An assignment whose `endDate` has already passed is left unchanged: it was only ever in force up to that date, and it still contributes to historical accrual. This operation is idempotent: it returns `204` whether or not an assignment was changed, including when no assignment carries the given ID, when the ID belongs to a different employee, and when the assignment is no longer live.

OAuth Scopes: time_off:policies.write

## Path parameters

- `employeeId` integer, required
- `assignmentId` integer, required

## Response `204`

The assignment was unassigned, or it was already not something that could be unassigned. No response body either way.

## Other responses

- `401`: Unauthorized. The credentials are missing or invalid.
- `403`: Forbidden. The authenticated user may not manage this employee's time off policy assignments.
- `404`: Employee not found. Note that an unknown assignment ID is a 204, not a 404 — only the employee in the path is checked for existence.

## Changes

- **2026-11-03** `922fc15f43a7`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/bamboohr/apis/bamboohr-api/changes/api/v1/employees/:employeeId/time-off/policies/:assignmentId/delete.md)

---

[API](https://skmtc.dev/bamboohr/apis/bamboohr-api.md) - [All operations](https://skmtc.dev/bamboohr/apis/bamboohr-api/llms.txt) - [OpenAPI document](https://skmtc.dev/bamboohr/apis/bamboohr-api/revisions/922fc15f43a7?raw)