> ## Documentation Index > Fetch the complete documentation index at: https://developers.chatwoot.com/llms.txt > Use this file to discover all available pages before exploring further. # Merge Contacts > Merge two contacts into a single contact. The base contact remains and receives all data from the mergee contact. After the merge, the mergee contact is permanently deleted. This action is irreversible. All conversations, labels, and custom attributes from the mergee contact will be moved to the base contact. ## OpenAPI ````yaml https://raw.githubusercontent.com/chatwoot/chatwoot/develop/swagger/tag_groups/application_swagger.json post /api/v1/accounts/{account_id}/actions/contact_merge openapi: 3.1.0 info: title: Chatwoot description: This is the API documentation for Chatwoot server. version: 1.1.0 termsOfService: https://www.chatwoot.com/terms-of-service/ contact: email: hello@chatwoot.com license: name: MIT License url: https://opensource.org/licenses/MIT servers: - url: https://app.chatwoot.com/ security: [] tags: - name: Account AgentBots description: Account-specific Agent Bots - name: Agents description: Agent management APIs - name: Canned Responses description: Pre-defined responses for common queries - name: Contacts description: Contact management APIs - name: Contact Labels description: Manage contact labels - name: Conversation Assignments description: Manage conversation assignments - name: Conversation Labels description: Manage conversation labels - name: Conversations description: Conversation management APIs - name: Custom Attributes description: Custom fields for contacts and conversations - name: Custom Filters description: Saved filters for conversations - name: Inboxes description: Communication channels setup - name: Integrations description: Third-party integrations - name: Labels description: Account label management APIs - name: Messages description: Message management APIs - name: Profile description: User profile APIs - name: Reports description: Analytics and reporting APIs - name: Teams description: Team management APIs - name: Webhooks description: Event notification webhooks - name: Automation Rule description: Workflow automation rules - name: Help Center description: Knowledge base management paths: /api/v1/accounts/{account_id}/actions/contact_merge: parameters: - $ref: '#/components/parameters/account_id' post: tags: - Contacts summary: Merge Contacts description: > Merge two contacts into a single contact. The base contact remains and receives all data from the mergee contact. After the merge, the mergee contact is permanently deleted. This action is irreversible. All conversations, labels, and custom attributes from the mergee contact will be moved to the base contact. operationId: contactMerge requestBody: required: true content: application/json: schema: type: object required: - base_contact_id - mergee_contact_id properties: base_contact_id: type: integer description: >- ID of the contact that will remain after the merge and receive all data example: 1 mergee_contact_id: type: integer description: >- ID of the contact that will be merged into the base contact and deleted example: 2 responses: '200': description: Contacts merged successfully content: application/json: schema: $ref: '#/components/schemas/contact_base' '400': description: Bad request - invalid contact IDs or contacts cannot be merged content: application/json: schema: $ref: '#/components/schemas/bad_request_error' '401': description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/bad_request_error' '404': description: One or both contacts not found content: application/json: schema: $ref: '#/components/schemas/bad_request_error' security: - userApiKey: [] components: parameters: account_id: in: path name: account_id schema: type: integer required: true description: The numeric ID of the account schemas: contact_base: allOf: - $ref: '#/components/schemas/generic_id' - $ref: '#/components/schemas/contact' bad_request_error: title: data type: object properties: description: type: string errors: type: array items: $ref: '#/components/schemas/request_error' generic_id: type: object properties: id: type: number contact: type: object properties: payload: type: array items: type: object properties: additional_attributes: type: object description: >- The object containing additional attributes related to the contact availability_status: type: string description: The availability status of the contact email: type: string description: The email address of the contact id: type: integer description: The ID of the contact name: type: string description: The name of the contact phone_number: type: string description: The phone number of the contact blocked: type: boolean description: Whether the contact is blocked identifier: type: string description: The identifier of the contact thumbnail: type: string description: The thumbnail of the contact custom_attributes: type: object description: The custom attributes of the contact example: attribute_key: attribute_value signed_up_at: dd/mm/yyyy last_activity_at: type: integer description: The last activity at of the contact created_at: type: integer description: The created at of the contact contact_inboxes: type: array items: $ref: '#/components/schemas/contact_inboxes' request_error: type: object properties: field: type: string message: type: string code: type: string contact_inboxes: type: object properties: source_id: type: string description: Contact Inbox Source Id inbox: $ref: '#/components/schemas/inbox_contact' inbox_contact: type: object properties: id: type: number description: ID of the inbox avatar_url: type: string description: The avatar image of the inbox channel_id: type: number description: The ID of the channel name: type: string description: The name of the inbox channel_type: type: string description: The type of the inbox provider: type: string description: The provider of the inbox securitySchemes: userApiKey: type: apiKey in: header name: api_access_token description: >- This token can be obtained by visiting the profile page or via rails console. Provides access to endpoints based on the user permissions levels. This token can be saved by an external system when user is created via API, to perform activities on behalf of the user. ````