Skip to main content
Pull the full record for one person. The response is the same shape the dashboard People detail page renders: primary email and phone, company, job title, and the channels and events the person has joined.

​
Synopsis

talkvalue path person get <id>

​
Arguments

ArgumentTypeDescription
<id>integerPerson ID. Use person list to find one.

​
Examples

​
1. Inspect a person in the terminal

talkvalue path person get 142
Prints a single-row table with the headline fields. Use --json if you need the nested company, channels, and events arrays.

​
2. Read one field with jq

talkvalue path person get 142 --json | jq -r '.data.primaryEmail.email'
Returns the primary email address as a raw string. primaryEmail is an object with email, type, and domain fields. Use .email to pull the address. Combine with other commands when you only need an identifier, for example, looking up an email before calling update.

​
3. Use inside a guard

if talkvalue path person get 142 --json >/dev/null 2>&1; then
  echo "Person 142 exists"
else
  echo "Person 142 not found"
fi
The CLI exits non-zero on 404 so the guard above branches cleanly. See Exit codes for the full mapping.

​
Response

{
  "data": {
    "id": 142,
    "name": "Alice Kim",
    "primaryEmail": { "email": "alice@acme.com", "type": "WORK", "domain": "acme.com" },
    "emails": [
      { "email": "alice@acme.com", "type": "WORK", "domain": "acme.com" }
    ],
    "primaryPhone": "+1-415-555-0199",
    "company": {
      "id": 88,
      "displayName": "Acme Inc.",
      "domain": "acme.com",
      "nameUpdatable": true
    },
    "jobTitle": "Head of Growth",
    "channels": [
      { "id": 7, "name": "Newsletter", "icon": null, "joinedAt": "2026-04-12T00:00:00Z" }
    ],
    "events": [
      { "id": 18, "name": "Spring Summit", "startAt": "2026-05-02T17:00:00Z", "joinedAt": "2026-05-02T00:00:00Z" }
    ],
    "mergeOperations": [],
    "createdAt": "2026-04-12T00:00:00Z"
  }
}
primaryEmail is an object with email, type, and domain fields. The full email list lives on emails. channels and events arrays are limited to the records the person currently belongs to. mergeOperations records every merge that produced this person; pass the entry’s id to person merge-undo to reverse one within the retention window.

​
See also