talkvalue path person delete

Remove a person from the active workspace. The CLI refuses to run without --confirm. There is no interactive prompt, so scripts have to opt in explicitly. Deletion is immediate. Restore is only possible from the dashboard’s activity history within the retention window.

Synopsis

talkvalue path person delete <id> --confirm

Arguments

Argument	Type	Description
`<id>`	integer	Person ID to delete. Use `person list` or `person get` to verify the target first.

Options

Flag	Type	Description
`--confirm`	flag	Required. The CLI exits with a usage error if you omit this flag.

Examples

1. Delete a single record

talkvalue path person delete 142 --confirm

Prints { "deleted": true, "id": 142 } as a table on success. Re-running the command on a missing ID returns a 404 and a non-zero exit code.

2. Pipe to jq for a clean assertion

talkvalue path person delete 142 --confirm --json \
  | jq -e '.data.deleted == true'

jq -e exits non-zero if deleted is anything but true, so the surrounding script fails closed.

3. Bulk delete from a file of IDs

while read -r id; do
  talkvalue path person delete "$id" --confirm --json \
    | jq -c '{id: .data.id, deleted: .data.deleted}'
done < ids-to-delete.txt

Process one ID per line. Capture stderr to a log file if you need to inspect failures separately.

Response

{
  "data": {
    "deleted": true,
    "id": 142
  }
}

The acknowledgement object is the only payload. The deleted person record itself is not returned. To recover history after a delete, inspect person activity on the original ID before issuing the delete.

​Synopsis

​Arguments

​Options

​Examples

​1. Delete a single record

​2. Pipe to jq for a clean assertion

​3. Bulk delete from a file of IDs

​Response

​See also