---
title: "People"
description: "The people behind your mentions, merged across accounts, with your tags, notes, mute and outreach."
canonical: https://docs.mentio.dev/guides/people
markdown: https://docs.mentio.dev/guides/people.mdx
---

# People

The people behind your mentions, merged across accounts, with your tags, notes, mute and outreach.

People are the humans behind your mentions, merged across their accounts. Use this to tag them, take notes, mute them and track outreach.

## List people [#list-people]

`GET /v1/people` returns one row per person. Each row holds their accounts, reach, public profile, stats for your workspace, your annotations and where your outreach stands. The list is offset-paginated with a `total`.

Filter by:

* platform, tag, follower range or mention counts
* intents seen, or keyword kinds mentioned or never mentioned
* outreach stage or owner
* `automated`: bot accounts, whose matched posts are mostly machine-made
* a saved segment (`segmentId`)

Everything you write about a person is your workspace's own. With `groupId`, every call works inside one keyword group instead, with its own people, annotations, merges, outreach and segments: see [Groups](/guides/groups#people-and-segments-by-group).

## Merge and split [#merge-and-split]

`POST /v1/people/{id}/merge` says an account and another person are the same human. Their mentions, tags, notes and outreach activities combine under the person named by `into`.

That person keeps its owner and stage unless it had none. Reading the merged account returns that person.

`POST /v1/people/{id}/split` makes the account its own person again.

## Tags, notes and mute [#tags-notes-and-mute]

`PATCH /v1/people/{id}` sets tags, notes, mute, the outreach owner (a workspace member; `null` clears) and stage.

A mute hides the person's posts from your feed, your alerts and your digests. Their posts are still ingested and billed.

## Outreach [#outreach]

Log every contact so two teammates never reach the same person without knowing:

* `POST /v1/people/{id}/activities` records that someone reached out: an email, a DM, a call. `memberId` defaults to the signed-in member; an API key that omits it logs an unattributed activity.
* The first activity claims an unowned person for whoever reached out and moves the stage from `not_contacted` to `contacted`. An existing owner and a later stage are kept, and an unattributed activity claims nobody.
* `GET /v1/people/{id}/activities` lists the contacts across all of the person's accounts, newest first (at most 200): who, the channel, when, and a short note. Read it before reaching out.
* `DELETE /v1/people/{id}/activities/{activityId}` removes one logged by mistake; the owner and stage stay as they are.

## Segments [#segments]

A segment is a named filter over your people (`/v1/segments`). It is evaluated on every read, so its count is the people in it right now.

* The list offers presets to save as a starting point.
* Pass a segment id as `segmentId` to `GET /v1/people` to list its members.
* With `groupId` a segment belongs to that group: listed, counted and changed only there, its name unique within the group.

The people list exports as CSV: see [Exports](/guides/exports#people-columns).

## Related [#related]

* [List people](/api/people/list-people): the endpoint reference.
* [Merge people](/api/people/merge-people): combine two accounts.
* [Segments](/api/segments/list-segments): saved people filters.
* [Groups](/guides/groups): people per customer.