# Employee

Endpoint: POST employee
Version: v1
Security: X-Signature

## Header parameters:

  - `X-Signature` (string, required)
    Example: "X-Signature: t=1492774577,v1=5257a869..."

## Request fields (application/json):

  - `version` (string)
    The version of the event.
    Example: "1"

  - `id` (string)
    The unique identifier for the event. This can be used as an idempotency key.
    Example: "c478966c-f927-411c-b919-179832d3d50c"

  - `timestamp` (integer)
    When the event occurred, formatted as a UNIX timestamp (in seconds).
    Example: 1698604061

  - `type` (string)
    The type of event that occurred.
    Enum: "CREATE", "UPDATE", "DELETE"

  - `category` (string)
    The category of the event.
    Enum: "ENTITY"

  - `description` (string)
    The description of the event. Note: this is subject to change and should not be used to match on this object.
    Example: "employee@example.com added"

  - `object` (string)
    The object that was created, updated or deleted.
    Enum: "EMPLOYEE"

  - `friendlyName` (string)
    The friendly name of this object. Note: this is subject to change and should not be used to match on this object.
    Example: "Employee"

  - `new` (object,null)
    This object represents an employee in your organization.

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

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

  - `new.firstName` (string)
    First name of the employee

Note: changes to this field do not trigger an UPDATE event
    Example: "John"

  - `new.lastName` (string)
    Last name of the employee

Note: changes to this field do not trigger an UPDATE event
    Example: "Hill"

  - `new.department` (string)
    Department - as provided by connected API integrations

Note: changes to this field do not trigger an UPDATE event
    Example: "Security Engineering"

  - `new.location` (string)
    Location - as provided by connected API integrations

Note: changes to this field do not trigger an UPDATE event
    Example: "New York"

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

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

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

  - `old` (object,null)
    This object represents an employee in your organization.

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

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

  - `old.firstName` (string)
    First name of the employee

Note: changes to this field do not trigger an UPDATE event
    Example: "John"

  - `old.lastName` (string)
    Last name of the employee

Note: changes to this field do not trigger an UPDATE event
    Example: "Hill"

  - `old.department` (string)
    Department - as provided by connected API integrations

Note: changes to this field do not trigger an UPDATE event
    Example: "Security Engineering"

  - `old.location` (string)
    Location - as provided by connected API integrations

Note: changes to this field do not trigger an UPDATE event
    Example: "New York"

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

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

  - `old.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 2XX fields