API · team

List team

GET /api/v2/team

Authorization

Authenticated user session (use inboxit login). Use the CLI login flow; a workspace API key cannot call this operation.

Parameters

All resource access is checked against the selected workspace and user permissions.

Request

Run inboxit login first. The CLI supplies authenticated user credentials.

Example

inboxit team list

Response

HTTP 200. Example values are illustrative; excerpts are marked.

Example

{
  "actor_id": "USER_UUID",
  "role": "owner",
  "workspace": "prod",
  "members": [],
  "invitations": []
}

Behavior & errors

Members include id, display_name, email and role. Pending invitations are visible to owner/admin only. workspace is the display name, not an object. Common errors: 400 invalid input, 401 unauthenticated, 403 insufficient permission, 404 missing/inaccessible resource, 409 conflict, 429 rate/usage limit, 503 service unavailable. See Errors & retries for recovery guidance.