jq or save as JSON. The dashboard company-detail page uses the same query.
Synopsis
Arguments
| Argument | Type | Description |
|---|---|---|
<companyId> | integer | Company ID. Use company list to find one. |
Options
| Flag | Type | Description |
|---|---|---|
--keyword <keyword> | string | Free-text match against name, email, phone, company, and job title. |
--channel-id <id> | integer (repeatable) | Limit to people also attributed to the given channel. |
--event-id <id> | integer (repeatable) | Limit to people also registered for the given event. |
--company-name <name> | string | Extra company display-name filter when the person’s record uses a different label. |
--job-title <title> | string | Limit by job title. |
--page <n> | integer | Page number (zero-indexed). Defaults to 0. |
--page-size <n> | integer | Page size. Defaults to the server default. |
--sort <value> | string (repeatable) | Sort expression field,direction (for example, joinedAt,desc). |
Examples
1. Browse the latest people at a company
88 as a table: ID, name, email, company, job title, joined-at, created-at.
2. Filter by event and pipe to jq
88 who also registered for event 18, projected to three fields.
3. Walk every page in a script
Response
pagination appears only in --json. companyName is a flattened convenience field. The full company object is also included so you can inspect nameUpdatable before company update.
See also
company get. Confirm company metadata first.path person list. Workspace-wide people query, same filter grammar.- Recipe: New registrants this week.
--sort createdAt,descdriven report. - Companies. The dashboard surface this command mirrors.
