# Unmerge employee

Endpoint: POST /v1/employees/{id}/unmerge
Version: v1
Security: x-api-key

## Path parameters:

  - `id` (string, required)
    Unique identifier for the employee

## Request fields (application/json):

  - `email` (string, required)
    The email address to unmerge from the target employee
    Example: "john.hill@example.com"

## Response 200 fields (application/json):

  - `id` (string)
    Unique identifier for the employee
    Example: "2a2197de-ad2c-47e4-8dcb-fb0f04cf83e0"

  - `email` (string)
    Primary email address of the employee
    Example: "john.hill@example.com"

  - `knownEmails` (array)
    All the known email addresses of the employee
    Example: ["john.hill@example.com","jhill@example.com"]

  - `firstName` (string)
    First name of the employee
    Example: "John"

  - `lastName` (string)
    Last name of the employee
    Example: "Hill"

  - `department` (string)
    Department - as provided by connected API integrations
    Example: "Security Engineering"

  - `location` (string)
    Location - as provided by connected API integrations
    Example: "New York"

  - `licensed` (boolean)
    Whether the employee is licensed on the Push platform
    Example: true

  - `groups` (array)
    Groups the employee is in
    Example: ["engineering","marketing"]

  - `creationTimestamp` (integer)
    When this employee was created, formatted as a UNIX timestamp (in seconds)
    Example: 1698669223

  - `chatopsEnabled` (boolean)
    Whether the employee has ChatOps enabledDeprecation notice: this value no longer does anything unless you still have access to the legacy Employee chat topics functionality on your account. It will be removed in the next API version.
    Example: true


## Response 400 fields

## Response 404 fields

## Response 500 fields