---
title: "Admin Allocate"
method: POST
path: "/api/asclepius/admin/assignments/allocate"
tags: ["asclepius-admin"]
---

# Admin Allocate

`POST /api/asclepius/admin/assignments/allocate`

## Request

- Base URL: `https://app.archangelhealth.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://app.archangelhealth.ai/api/asclepius/admin/assignments/allocate`
- Auth: none declared

Propose an allocation, and commit it only when asked.

THE POINT: the allocator proposes and an admin commits. The response is a
table an operator reads and adjusts, and a case nothing could be proposed
for comes back in ``unassigned`` WITH A REASON rather than quietly vanishing
from the list.

Committing writes ``assignments`` rows, which are a PRIORITY and not a
permission: an assigned case sorts to the top of its assignee's queue and
every other physician still sees it exactly where it was. Nothing about who
MAY draw a case changes here.

## Headers

- `authorization` string, nullable

## Request body

- AllocateBody: Which cases to allocate, and to whom. ``dry_run`` defaults to TRUE. Same shape as ingest promotion, and for the same reason: an admin should be able to iterate on an allocation before a physician is told to do anything.
  - `task_ids` string[]
  - `labels_per_case` integer
  - `reviewers_per_case` integer
  - `max_share` number
  - `dry_run` boolean
  - `due_at` string, nullable
  - `exclusive_hours` integer, nullable
  - `user_ids` string[], nullable
  - `specialty` string, nullable
  - `to_all` boolean
  - `roles` object, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/archangelhealth/apis/archangel-health-surgical-patient-platform.md) - [All operations](https://skmtc.dev/archangelhealth/apis/archangel-health-surgical-patient-platform/llms.txt) - [OpenAPI document](https://skmtc.dev/archangelhealth/apis/archangel-health-surgical-patient-platform/revisions/3514f4e119da?raw)