---
title: "Retrieve a user"
method: GET
path: "/v1/users/{id}"
tags: ["User"]
---

# Retrieve a user

`GET /v1/users/{id}`

Returns a single user by id (the Firebase UID). A normal user can only fetch
their own record; Cardda staff can fetch any. Includes the user's memberships
and computed profile methods. This endpoint is **not company-scoped** (it is
on the `company-id` header whitelist).

## Path parameters

- `id` string, required

## Response `200`

The requested user.

- User — An individual user (Firebase-authenticated). The `id` is the Firebase UID. Internal attributes (`ever_paid`, `roles`, `statistics`, ...) are **not part of the documented public contract** and are intentionally omitted here. The supported user shape is documented below.
  - `id` string, required — Firebase UID.
  - `first_name` string, nullable
  - `last_name` string, nullable
  - `email` string, nullable
  - `phone` integer, nullable
  - `identifier` string, nullable — Tax id / national id of the user.
  - `country` string, nullable
  - `nationality` string, nullable
  - `address` string, nullable
  - `occupation` string, nullable
  - `gender` integer, nullable
  - `birthdate` string, date-time, nullable
  - `is_pep` boolean — Whether the user is a politically exposed person.
  - `legal_address` object, nullable
  - `user_type` string, nullable
  - `status` string
  - `terms_accepted` boolean
  - `legal_representative` boolean, nullable
  - `has_powers_to_act` boolean, nullable
  - `whatsapp_verified` boolean
  - `milestone_ids` string[] — Computed list of milestone ids reached by the user.
  - `n_companies` integer — Number of companies the user belongs to (computed).
  - `company_role` string, nullable — The user's role in the current company context (computed).
  - `plh_profile_complete` boolean — Whether the user's PLH profile is complete (computed; serialized as `plh_profile_complete?`).
  - `missing_plh_profile_fields` string[]
  - `needs_password_setup` boolean — Whether the user still needs to set a password (computed; serialized as `needs_password_setup?`).
  - `created_at` string, date-time
  - `updated_at` string, date-time

## Other responses

- `401` — Unauthorized
- `404` — User not found

---

[API](https://skmtc.dev/cardda/apis/banking-api.md) · [All operations](https://skmtc.dev/cardda/apis/banking-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/cardda/banking-api/revisions/ff1aeb3fda8b/schema)