---
title: "Hs Invite Claim"
method: POST
path: "/api/asclepius/hs/invite/{token}/claim"
tags: ["asclepius-provider"]
---

# Hs Invite Claim

`POST /api/asclepius/hs/invite/{token}/claim`

## 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/invite/{token}/claim`
- Auth: none declared

Spend an invite: set a name and a password, and sign in.

Signs them straight into the portal rather than bouncing to the login form,
for the same reason ``/hs/signup/verify`` does: the username was derived
from their organization's name and they have never seen it, so "now enter
your username" would strand every single person this letter reaches.

Single use is enforced by the store, which clears the hash in the same
statement that writes the password. A second visit to the link therefore
finds nothing, which is the correct answer: the account now has an owner.

## Path parameters

- `token` string, required

## Request body

- HsInviteClaimRequest: What the claim screen sends. NO EMAIL FIELD, deliberately. The account's address is whatever the invite was minted against, and the body is written by whoever holds the link. Letting it name the address would make a forwarded invite a way to attach an account on somebody else's organization to an address of your choosing, which is the exact hole ``/hs/members`` closes by taking the organization from the session.
  - `full_name` string
  - `password` string, required

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