This endpoint creates a deactivated employee in Kenjo (isActive = false). To activate the employee use the put /activate method; an activation message will be sent to the employee email to complete the activation through the onboarding wizard.


Required body

You must send the objects account, personal and work with at least:

• account: email (required, must be unique in the organization).

• personal: firstName and lastName (required, non-empty strings).

• work: companyId and weeklyHours (required).

If any of these are missing or invalid (e.g. empty name, duplicate email), the API returns 400 Bad Request and no employee is created.


Optional fields and defaults

• workSchedule — Optional. If you omit it, the API uses the company's working days. If the company has no working days defined, it defaults to Monday–Friday.

• language (inside account) — Optional. If omitted, the company's default language is assigned.


Custom fields

You can send custom fields for the personal, work, address, financial and home sections. Use each field's API name (prefix c_ and the field name without spaces). The value must match the type defined for that custom field in Kenjo.



Example — custom field Activity type in work (List with values "1", "2", "3"):

...
{
...
  "work": {
    "c_Activitytype": "1",
    ...
  },
...
}

If you send a value or type that does not match the field definition, the request returns 400.


If the operation succeeds, an inactive employee is created and the response includes the provided information and the Kenjo _id for the new employee.