jq or save as JSON. The dashboard People page uses the same backend query.
Synopsis
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 in the given channel. Repeat to OR multiple. |
--event-id <id> | integer (repeatable) | Limit to people registered for the given event. Repeat to OR multiple. |
--company-id <id> | integer | Limit by company ID. |
--company-name <name> | string | Limit by company display name. |
--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, createdAt,desc). Repeat for secondary sorts. |
Examples
1. Browse the latest people
2. Filter by channel and pipe to jq
7 or 12, stripped to the three fields. The --json envelope also carries .pagination.
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.
See also
person get. Fetch a single record in full detail.person export. Stream every person as CSV.- Recipe: New registrants this week.
--sort createdAt,descdriven report. - Recipe: Channel analysis.
--channel-idfiltering in scripts. - People. The dashboard surface this command mirrors.
