# Update an employee

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

## Security:

  - `x-api-key` (unknown)
    apiKey in header x-api-key

## Path parameters:

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

## Request fields (application/json):

  - `email` (string)
    A new primary email address for the employee. This must be one of the known email addresses for the employee.

  - `firstName` (string)
    A new first name for the employee

  - `lastName` (string)
    A new last name for the employee

  - `chatopsEnabled` (boolean)
    Set 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.

  - `licensed` (boolean)
    Set whether the employee is licensed on the Push platform

  - `groups` (array)
    Set the groups an employee is in (this will overwrite the existing groups)

## Response 200:

  - `200` (unknown)
    OK. Returns `null` if you unlicense an employee that hasn't got any accounts

## 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

  - `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

  - `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

## Response 400:

  - `400` (unknown)
    Bad Request with status EMPLOYEE_NOT_LICENSED, EXCEEDED_MAX_LICENSED_EMPLOYEES or CHATOPS_NOT_IN_WORKING_STATE

## Response 404:

  - `404` (unknown)
    Employee Not Found