Get user info

GET 
/user.info

Resolve a v1 principal by ID, or look up a workspace member by email.

ID lookup resolves active or archived members, guests, and authorized automated actors (classic bots, agents, assistants, and coworkers). The response always includes type: "user" | "bot"; guests additionally have isGuest: true. Groups, unknown IDs, and automated actors outside the caller's Roam/account/owner boundary return user_not_found.

Email lookup remains workspace-member-only. Personal access tokens and the MCP user_info tool may use ID lookup.

Provide either id or email, not both.

See Identity & Principals for the taxonomy, visibility rules, and directory-versus-hydration guidance.

Required scope: user:read (add user:read.email to look up by email or include email in response, user:read.status to expand presence status, availability, and willReturn)

Access: Organization and Personal.

---

OpenAPI Spec: chat-v1.json

Request

Responses

200

Principal info retrieved successfully

400

Bad request. Common causes:

• Neither id nor email provided
• Both id and email provided

401

Presented invalid authentication credentials.

403

Forbidden. Common causes:

• Looking up by email requires user:read.email scope

404

Principal not found, not authorized, or the ID belongs to a group (user_not_found).

405

An unsupported method was requested.

500

An internal error occurred.