---
title: "Create Hs Data Request"
method: POST
path: "/api/asclepius/admin/hs-requests"
tags: ["asclepius-admin"]
---

# Create Hs Data Request

`POST /api/asclepius/admin/hs-requests`

## 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/hs-requests`
- Auth: none declared

Write the request down, then enqueue one letter per active member of every
partner that may upload.

The enqueue is synchronous and the SEND is not. That split is the whole
design: the operator finds out immediately whether the request was recorded
and how many people it will reach, and nothing about their request depends on
an email provider being up.

## Headers

- `authorization` string, nullable

## Request body

- HsDataRequestBody: One of two shapes (Case Generation Fix PRD §B4). The console now sends a MESSAGE and a list of recipients: the message is the request, and the four structured fields (what / specialty / how many / by when) are optional colour. The original structured shape is still accepted unchanged, because the partner portal and the letter render those fields when they are present, and nothing that sent them should start failing.
  - `message` string
  - `recipient_hs_ids` string[], nullable
  - `title` string
  - `specialty` string
  - `case_count` integer
  - `due_date` string
  - `details` string

## 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)