> For the complete documentation index, see [llms.txt](https://docs.adaptria.locaria.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adaptria.locaria.com/client-api/reference/users.md).

# 👥 Users

### Users

Authenticated principal info (`/me`) and internal staff directory. `/me` is available to every authenticated caller (static API key or OAuth/JWT). List and get-by-id endpoints are internal-only — client API keys receive `403`.

## Who am I — current authenticated user

> Returns the currently authenticated principal regardless of credential type (static API key or OAuth/JWT). Available to every authenticated caller — internal staff and client users alike. The \`authMethod\` field identifies which credential produced the session so MCP clients and audit consumers can distinguish dashboard sessions from automation traffic.

```json
{"openapi":"3.1.0","info":{"title":"Adaptria Public API: Client","version":"1.0.0"},"tags":[{"name":"👥 Users","description":"## Users\n\nAuthenticated principal info (`/me`) and internal staff directory. `/me` is available to every authenticated caller (static API key or OAuth/JWT). List and get-by-id endpoints are internal-only — client API keys receive `403`.\n"}],"servers":[{"url":"https://api.adaptria.locaria.com","description":"Production Environment"}],"security":[{"apiKeyAuth":[]}],"components":{"securitySchemes":{"apiKeyAuth":{"type":"apiKey","in":"header","name":"Api-key","description":"## API Key Authentication\n\nStatic API key obtained from the Adaptria Portal or via `POST /api/credentials/api-keys`.\n\n**How to authenticate**:\n1. Generate an API key from the Adaptria Portal (Settings → API Keys) or ask your admin\n2. Include the key in all requests using the `Api-key` header\n\n**Key format**: `lla_live_<32-character-string>`\n\n**No token exchange needed** — the key is used directly in every request. Revoke or rotate keys from the portal."}},"schemas":{"GetCurrentUserResponse":{"type":"object","properties":{"success":{"type":"boolean","enum":[true]},"data":{"$ref":"#/components/schemas/CurrentUser"}},"required":["success","data"]},"CurrentUser":{"type":"object","properties":{"id":{"type":"string","format":"uuid","description":"Universally Unique Identifier (UUID v4)"},"email":{"type":"string","format":"email"},"firstName":{"type":["string","null"]},"lastName":{"type":["string","null"]},"roleCode":{"type":"string","description":"Role code of the authenticated principal"},"authMethod":{"type":"string","description":"Credential type that produced the session: auth0_jwt, static_api_key, custom_jwt"}},"required":["id","email","roleCode"]}}},"paths":{"/api/public/v1/users/me":{"get":{"summary":"Who am I — current authenticated user","description":"Returns the currently authenticated principal regardless of credential type (static API key or OAuth/JWT). Available to every authenticated caller — internal staff and client users alike. The `authMethod` field identifies which credential produced the session so MCP clients and audit consumers can distinguish dashboard sessions from automation traffic.","tags":["👥 Users"],"responses":{"200":{"description":"Authenticated user","content":{"application/json":{"schema":{"$ref":"#/components/schemas/GetCurrentUserResponse"}}}},"401":{"description":"Authentication required"},"404":{"description":"Authenticated user no longer exists"}}}}}}
```