# Finding

Endpoint: POST finding
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: "MFA not registered finding observed for user@example.com on Google Workspace"

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

  - `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: "Finding"

  - `new` (object)
    This object represents a finding in your organization.

  - `new.id` (string)
    Unique identifier for the finding
    Example: "d6a32ba5-0532-4a66-8137-48cdf409c972"

  - `new.type` (string)
    The type of finding
    Enum: "MFA_NOT_REGISTERED", "REUSED_PASSWORD", "SHARED_ACCOUNT", "UNUSED_THIRD_PARTY_APP", "WEAK_PASSWORD", "LEAKED_PASSWORD", "PASSWORD_MANAGER_NOT_USED", "STOLEN_CREDENTIALS"

  - `new.state` (string)
    The state of the finding
    Enum: "OPEN", "RESOLVED"

  - `new.employeeId` (string,null)
    ID of the employee this finding is linked to, null if finding is not linked to an employee.
    Example: "379ac7ea-ff2a-42ef-af37-06d2020dc46a"

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

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

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

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

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

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

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

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

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

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

  - `new.passwordId` (string,null)
    ID of the password this finding is linked to, null if finding is not linked to a password.
    Example: "c4a045a1-5331-4714-af83-6a361e98960d"

  - `new.accountId` (string,null)
    ID of the account this finding is linked to, null if finding is not linked to an account.

  - `new.appType` (string,null)
    The type of app this finding is linked to, null if finding is not linked to an app.
    Example: "PUSH_SECURITY"

  - `new.appId` (string,null)
    ID of the app this finding is linked to, null if finding is not linked to an app.
    Example: "2a2197de-ad2c-47e4-8dcb-fb0f04cf83e0"

  - `new.creationTimestamp` (integer)
    When this finding was first observed, formatted as a UNIX timestamp (in seconds)
    Example: 1698064423

  - `old` (object)
    This object represents a finding in your organization.


## Response 2XX fields