> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blobhub.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Get User

Retrieve information about a specific user.

## **GET** `/users/:id`

### Path Parameters

| Parameter | Type   | Required | Description                                     |
| :-------- | :----- | :------- | :---------------------------------------------- |
| `id`      | string | Yes      | The unique ID or alias of the user to retrieve. |

### Response

| Parameter | Type   | Description           |
| :-------- | :----- | :-------------------- |
| `user`    | object | The user object data. |

### Example

<CodeGroup>
  ```bash Request theme={null}
  curl -X GET https://api.blobhub.io/v1/users/user_123
  ```

  ```json Response theme={null}
  {
    "status": "success",
    "user": {
      "id": "user_123",
      "name": "Jane Doe",
      "alias": "janedoe",
      "type": "human",
      "status": "active",
      "role": "read"
    }
  }
  ```
</CodeGroup>

<Note>
  `type` (`human` or `service`) and `status` (`active` or `retired`) appear on every user object — see
  [Service Accounts](/general/service-accounts) for what a `service` account is and what `retired` means for
  one.
</Note>

### Identifier

The `id` parameter accepts a UUID, alias, or [`me`](/rest-api/conventions#the-me-alias).

### Permissions

Any authenticated caller can retrieve any user's full record — there is no self/other distinction and no
field redaction on this endpoint. The only thing that changes with the caller is `role`, which is injected
onto the response and is never a stored attribute of the account itself:

| Caller | `role` in the response |
| :----- | :--------------------- |
| Self   | `owner`                |
| Other  | `read`                 |

Read access is unrestricted; write access is not — [Update User](/rest-api/users/update-user) is still
self-only (or owner-only, for a service account).