---
title: "Admin Release Earning Hold"
method: POST
path: "/api/asclepius/admin/earnings/{earning_id}/release"
tags: ["asclepius-payments"]
---

# Admin Release Earning Hold

`POST /api/asclepius/admin/earnings/{earning_id}/release`

## 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/earnings/{earning_id}/release`
- Auth: none declared

Decide a proposed pay reduction.

THE POINT OF THIS ENDPOINT: the algorithm never applies a pay cut on its
own. It computes a multiplier, and a row it wants to pay below the posted
rate is held until a person acts here. An automated reduction and a proposed
reduction a human approves are materially different objects, legally and
ethically, and this route is the difference between them.

``pay_full_rate`` overrides the proposal and pays the posted rate, because
the person deciding is allowed to disagree with the model. Either way the
decision is attributed and timestamped: reducing a physician's pay is
consequential and an unattributable reduction cannot be appealed.

Releasing does not itself approve the row. It removes the hold, and the
normal ledger rules (a verdict, or the auto-approve window) then apply, so
this endpoint decides ONE question and does not quietly decide others.

## Path parameters

- `earning_id` string, required

## Headers

- `authorization` string, nullable

## Request body

- ReleaseHoldBody
  - `pay_full_rate` boolean
  - `note` 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)