How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Kenjo Employees API

Employee records and their profile sections.

Kenjo Employees API is one of 8 APIs that Kenjo publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Employees. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 22 operations across 21 paths, and defines 9 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://api.kenjo.io/api/v1, https://sandbox-api.kenjo.io/api/v1.

22 operations 21 paths 9 schemas 11 GET1 POST10 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.kenjo.io/api/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Kenjo Employees API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Bearer token obtained from POST /auth/login by exchanging a Kenjo API key.

Paths & Operations 22

Across 21 paths, the API surfaces 22 operations — 11 GET, 1 POST, 10 PUT. Each is listed below with its method, path, parameters, and response codes.

Employees 22

Employee records and their profile sections.

GET
/user-accounts
List user accounts
listUserAccounts → 200401
GET
/employees
List employees
listEmployees 2 params → 200401
POST
/employees
Create a new employee
createEmployee body → 201401
GET
/employees/{employeeId}
Get an employee
getEmployee 1 param → 200401404
GET
/employees/accounts
List employee accounts
listEmployeeAccounts → 200401
GET
/employees/personals
List employee personal information
listEmployeePersonals → 200401
GET
/employees/works
List employee work information
listEmployeeWorks → 200401
GET
/employees/work-schedules
List employee work schedules
listEmployeeWorkSchedules → 200401
GET
/employees/addresses
List employee addresses
listEmployeeAddresses → 200401
GET
/employees/financials
List employee financial data
listEmployeeFinancials → 200401
GET
/employees/homes
List employee home information
listEmployeeHomes → 200401
GET
/employees/emergencies
List employee emergency contacts
listEmployeeEmergencies → 200401
PUT
/employees/{employeeId}/accounts
Update employee account section
updateEmployeeAccount 1 param body → 200401
PUT
/employees/{employeeId}/personals
Update employee personal section
updateEmployeePersonal 1 param body → 200401
PUT
/employees/{employeeId}/works
Update employee work section
updateEmployeeWork 1 param body → 200401
PUT
/employees/{employeeId}/work-schedules
Update employee work schedule section
updateEmployeeWorkSchedule 1 param body → 200401
PUT
/employees/{employeeId}/addresses
Update employee address section
updateEmployeeAddress 1 param body → 200401
PUT
/employees/{employeeId}/financials
Update employee financial section
updateEmployeeFinancial 1 param body → 200401
PUT
/employees/{employeeId}/homes
Update employee home section
updateEmployeeHome 1 param body → 200401
PUT
/employees/{employeeId}/emergencies
Update employee emergency section
updateEmployeeEmergency 1 param body → 200401
PUT
/employees/{employeeId}/activate
Activate an employee
activateEmployee 1 param → 200401
PUT
/employees/{employeeId}/deactivate
Deactivate an employee
deactivateEmployee 1 param → 200401

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are EmployeeInput (5 properties), GenericList (4 properties), Error (2 properties). Each schema is shown below with its type and property counts.

Employee
GenericList
object
4 properties
EmployeeAccountList
EmployeeList
Error
object
2 properties
SectionList
EmployeeInput
object
5 properties 1 required
UserAccountList
Section
object
A profile section payload. Field set varies by section (account, personal, work, etc.).

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

kenjo-employees-api-openapi.yml Raw ↑

Other APIs Kenjo publishes across the network.

Kenjo Attendance API
Kenjo Authentication API
Kenjo Compensation API
Kenjo Documents API
Kenjo Organization API
Kenjo Recruiting API
Kenjo Time Off API
Where this information came from

This is an independent, third-party profile of Kenjo Employees API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.