--- title: "Merge two persons" method: PUT path: "/persons/{id}/merge" tags: ["Persons"] --- # Merge two persons `PUT /persons/{id}/merge` Merges a person with another person. For more information, see the tutorial for merging two persons. ## Path parameters - `id` integer, required ## Request body - object - `merge_with_id` integer, required — The ID of the person that will not be overwritten. This person’s data will be prioritized in case of conflict with the other person. ## Response `200` Success - object - `success` boolean — If the response is successful or not - `data` object - `id` integer — The ID of the person - `company_id` integer — The ID of the company related to the person - `active_flag` boolean — Whether the person is active or not - `phone` object[] — A phone number supplied as a string or an array of phone objects related to the person. The structure of the array is as follows: `[{ "value": "12345", "primary": "true", "label": "mobile" }]`. Please note that only `value` is required. - `value` string — The phone number - `primary` boolean — Boolean that indicates if phone number is primary for the person or not - `label` string — The label that indicates the type of the phone number. (Possible values - work, home, mobile or other) - `email` object[] — An email address as a string or an array of email objects related to the person. The structure of the array is as follows: `[{ "value": "mail@example.com", "primary": "true", "label": "main" } ]`. Please note that only `value` is required. - `value` string — Email - `primary` boolean — Boolean that indicates if email is primary for the person or not - `label` string — The label that indicates the type of the email. (Possible values - work, home or other) - `first_char` string — The first letter of the name of the person - `add_time` string — The date and time when the person was added/created. Format: YYYY-MM-DD HH:MM:SS - `update_time` string — The last updated date and time of the person. Format: YYYY-MM-DD HH:MM:SS - `visible_to` string — The visibility group ID of who can see the person - `picture_id` object, nullable - `id` integer — The ID of the picture associated with the item - `item_type` string — The type of item the picture is related to - `item_id` integer — The ID of related item - `active_flag` boolean — Whether the associated picture is active or not - `add_time` string — The add time of the picture - `update_time` string — The update time of the picture - `added_by_user_id` integer — The ID of the user who added the picture - `pictures` object - `128` string — The URL of the 128*128 picture - `512` string — The URL of the 512*512 picture - `label` integer, nullable — The label assigned to the person. When the `label` field is updated, the `label_ids` field value will be overwritten by the `label` field value. - `label_ids` integer[] — The IDs of labels assigned to the person. When the `label_ids` field is updated, the `label` field value will be set to the first value of the `label_ids` field. - `org_name` string, nullable — The name of the organization associated with the person - `owner_name` string — The name of the owner associated with the person - `cc_email` string, nullable — The BCC email associated with the person - `owner_id` integer — The ID of the owner related to the person - `org_id` integer — The ID of the organization related to the person - `merge_what_id` integer — The ID of the person with what the main person was merged - `name` string — The name of the person - `first_name` string — The first name of the person - `last_name` string, nullable — The last name of the person - `email_messages_count` integer — The count of email messages related to the person - `activities_count` integer — The count of activities related to the person - `done_activities_count` integer — The count of done activities related to the person - `undone_activities_count` integer — The count of undone activities related to the person - `files_count` integer — The count of files related to the person - `notes_count` integer — The count of notes related to the person - `followers_count` integer — The count of followers related to the person - `last_incoming_mail_time` string, nullable — The date and time of the last incoming email associated with the person - `last_outgoing_mail_time` string, nullable — The date and time of the last outgoing email associated with the person - `open_deals_count` integer — The count of open deals related with the item - `related_open_deals_count` integer — The count of related open deals related with the item - `closed_deals_count` integer — The count of closed deals related with the item - `related_closed_deals_count` integer — The count of related closed deals related with the item - `won_deals_count` integer — The count of won deals related with the item - `related_won_deals_count` integer — The count of related won deals related with the item - `lost_deals_count` integer — The count of lost deals related with the item - `related_lost_deals_count` integer — The count of related lost deals related with the item - `next_activity_date` string, nullable — The date of the next activity associated with the deal - `next_activity_time` string, nullable — The time of the next activity associated with the deal - `next_activity_id` integer, nullable — The ID of the next activity associated with the deal - `last_activity_id` integer, nullable — The ID of the last activity associated with the deal - `last_activity_date` string, nullable — The date of the last activity associated with the deal - `participant_open_deals_count` integer — The count of open participant deals related with the item - `participant_closed_deals_count` integer — The count of closed participant deals related with the item --- [API](https://skmtc.net/pipedrive/apis/pipedrive-api-v1.md) · [All operations](https://skmtc.net/pipedrive/apis/pipedrive-api-v1/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pipedrive/pipedrive-api-v1/revisions/bf863a979545/schema)