asclepius-provider
Hs Agreement Sign
Take one signature, render the record, and open the upload door.
The order of operations is the whole of it, and it is deliberate:
- verify the state, the affirmations, and that the text has not changed underneath the signer;
- render the PDF and store it, so a row can never point at a document that does not exist;
- INSERT the signature row -- append-only, enforced by trigger;
- move the organization to active;
- 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.
post/api/asclepius/hs/agreement/sign
Request
- Base URLhttps://app.archangelhealth.ai (the document declares no server; this is the origin it was published from)
- URLhttps://app.archangelhealth.ai/api/asclepius/hs/agreement/sign
- Authnone declared
Request body
Response
Successful Response
unknown required
Changes
No recorded changes to this operation across all 1 revision of this API.