---
title: "Hs Agreement Sign"
method: POST
path: "/api/asclepius/hs/agreement/sign"
tags: ["asclepius-provider"]
---

# Hs Agreement Sign

`POST /api/asclepius/hs/agreement/sign`

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

Take one signature, render the record, and open the upload door.

The order of operations is the whole of it, and it is deliberate:

  1. verify the state, the affirmations, and that the text has not changed
     underneath the signer;
  2. render the PDF and store it, so a row can never point at a document
     that does not exist;
  3. INSERT the signature row -- append-only, enforced by trigger;
  4. move the organization to `active`;
  5. mail the copies, in the background.

A failure at step 2 leaves nothing signed. A failure at step 5 leaves an
agreement that is signed and an email that did not arrive, which is the
right way round: the signature is the fact, the email is a copy of it.

## Request body

- HsAgreementSignRequest: The four things a clickwrap has to capture, named separately. One "I agree" boolean would be cheaper and would collapse two legally distinct affirmations into one: authority to bind the organization, and consent to transact electronically. Courts test them separately, so the record keeps them separate.
  - `typed_name` string, required
  - `typed_title` string, required
  - `authority_affirmed` boolean
  - `consent_esign` boolean
  - `doc_sha256` 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)