---
title: "Who becomes overallocated if some tasks take proposed dates"
method: POST
path: "/scheduling/projects/{id}/what-if-overallocation"
tags: ["scheduling"]
---

# Who becomes overallocated if some tasks take proposed dates

`POST /scheduling/projects/{id}/what-if-overallocation`

## Request

- Base URL: `https://api.onplana.com/api`
- URL: `https://api.onplana.com/api/scheduling/projects/{id}/what-if-overallocation`
- Auth: one of:
  - HTTP bearer
  - API key in header `Authorization`

Read-only. Runs the resource leveler's check twice, on the project as it stands and with the proposed dates in place, and returns each person and week over capacity in the second run and not in the first. Writes nothing. Needs read access to the project. Only while the server switch gantt_what_if_enabled is on; off, it answers 404.

## Path parameters

- `id` string, required

## Headers

- `X-Organization-Id` string, required

## Request body

- object
  - `moves` object[], required
    - `taskId` string, required
    - `startDate` string, date, required
    - `dueDate` string, date, required

## Response `200`

`{ overallocations }`: userId, userName, weekStart, allocatedHours, capacityHours, overageHours and taskIds per person and week

---

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