---
title: "Me"
method: GET
path: "/api/asclepius/auth/me"
tags: ["asclepius"]
---

# Me

`GET /api/asclepius/auth/me`

## 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/auth/me`
- Auth: none declared

The signed-in physician, and the tick of the onboarding cadence clock.

Welcome package v2 §5: ``sessions_seen`` increments on the ``/auth/me`` that
follows a login — not in ``/auth/login``, because the portal also reaches
this endpoint on a cold boot from a token still in storage, and a physician
who closes the tab on Monday and opens it on Tuesday has started a session
without signing in again.

Idempotent per LOGIN, keyed on the token's ``jti``: a reload, a second tab
and the parallel calls one page paint makes all carry the same token and
count once, while a genuine new sign-in mints a new one and counts. Without
that key the clock would run at the speed of page loads and every physician
would be past the re-entry page before they had seen it twice.

Best-effort by construction. This endpoint is how the portal learns who it is
talking to, and a counter that cannot write is not a reason to fail that.

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