Skip to main content

Overview

GET /v1/users lists the people in your workspace: admins and members, whether or not they send from an identity. Use it to keep a seat inventory of Enginy next to your other tools.

Who can call it

  • The API key needs the USERS_READ scope, or ALL. USERS_READ is read-only and grants nothing else.
  • The key must have been created by a workspace admin. A key created by a member gets 403. Over MCP, connect as a workspace admin.

List users

Filter with role=admin or role=member, and with search (name or email). Page with page and pageSize (at most 100); meta.total is the number of users that match.

Who is listed

Every current admin and member of the workspace. These are not listed:
  • Pending invitations. A person appears once they accept.
  • Removed users.
  • Enginy staff with access to your workspace.
  • Staff of an organization (agency) who manage your workspace from that organization.
  • CRM owners that Enginy keeps for task assignment. List those with GET /v1/tasks/owners.

Users and identities

A user is a person who logs in to Enginy. An identity is a sending account (LinkedIn, email) that users send from. A user may send from no identity, and several users can share one. The workspace capacity counts identities, not users: GET /v1/workspace returns identities.used and identities.max. The number of users can therefore differ from what the workspace is billed for. To list the sending accounts, use GET /v1/identities.