---
title: "Diagnose which org this identity resolves to and whether its devices are visible"
method: GET
path: "/v1/products/{product}/whoami"
tags: ["Account"]
---

# Diagnose which org this identity resolves to and whether its devices are visible

`GET /v1/products/{product}/whoami`

## Request

- Base URL: `https://api.sqai.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.sqai.com/v1/products/{product}/whoami`
- Auth: none declared

Read-only self-diagnosis for the CLI-login path. For the CALLER only: which org does the identity link point at, does that org still exist, and how many active devices does it hold. `link_dangling: true` — or a device count that disagrees with what the CLI just registered — is the signature of the identity-link drift that makes the portal report 'No devices registered yet' while `<product> login` reports success.

## Path parameters

- `product` string, required

## Headers

- `authorization` string, nullable

## Response `200`

Successful Response

- object

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/sqai/apis/algenta-control-plane.md) · [All operations](https://skmtc.dev/sqai/apis/algenta-control-plane/llms.txt) · [OpenAPI document](https://skmtc.dev/sqai/apis/algenta-control-plane/revisions/f30391a81130?raw)
