Skip to main content
A person is the human behind one or more contact records. When the same human shows up through more than one channel, for example their work email from an email campaign and their LinkedIn profile from a LinkedIn campaign, contacts for that person are shown as one person in RevyOps. For how merging and splitting people works from the RevyOps UI, see the People user guide.

​
Configuration

​
Attributes

There’s no POST or PATCH on /public/people: a person’s identity fields come from its contact records, which you create and update through the Contacts endpoints. The only writes on people are merge and split.

​
Relationships

  • Contacts: one-to-many. A person has one or more contact records; each contact belongs to exactly one person. See Contacts.
  • Companies: indirect, through contacts. A person doesn’t have its own company; each of its contacts can belong to a company, and emails/linkedin_urls/phones items each carry the company_id of the contact they came from.

​
Merging and Splitting

  • Merge (POST /public/people/merge) combines every contact record from a list of people into one. The first ID in person_ids becomes the primary person; the rest are merged into it. Requires at least 2 person IDs.
  • Split (POST /public/people/split) moves the contact_ids you specify off of person_id and onto a newly created person. The source person must keep at least one contact.
Merge and split require a master-level API key. See Authentication.
RevyOps doesn’t currently expose dedicated MCP tools for people. Use the query_entity MCP tool against the contact entity, or the REST endpoints above, to work with people programmatically.