---
title: "Load V4 Real Cases"
method: POST
path: "/api/asclepius/generation/load-v4-real-cases"
tags: ["asclepius"]
---

# Load V4 Real Cases

`POST /api/asclepius/generation/load-v4-real-cases`

## 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/generation/load-v4-real-cases`
- Auth: none declared

Load the three V4 REAL de-identified cases as ``partner_ehr`` tasks
(V4 Cases & Promotion PRD §3).

The real-data sibling of ``/generation/{specialty}/load-gold``: no LLM needed
(each case ships with its authored A/B preference pair), idempotent on a
stable ``v4real-<case_id>`` task id.

``holds`` in the response names any case the content gate is holding OUT of
the queue and why. A non-empty ``holds`` is the honest answer to "did all
three ship?" — read it rather than the ``loaded`` count.

## Query parameters

- `specialty` string, nullable: Load only this specialty's V4 cases; omit for all.
- `max_labels` integer: Independent labels per case. Default 3 (one labeller + two for Cohen's kappa). This is what we PAY for, it is not how many physicians can SEE the case.
- `open_to_all_specialties` boolean, nullable: Show these cases to every approved physician, bypassing specialty routing. VISIBILITY only, it does not change max_labels or what we pay. Omit to follow ASCLEPIUS_V4_OPEN_TO_ALL (default on), which is what the boot seeder uses; pass it explicitly to override for this call.

## Headers

- `authorization` string, 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)