Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Kenjo Organization API

Companies, offices, departments, teams, areas, and calendars.

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

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

This API exposes 25 operations across 13 paths, and defines 3 schemas. It is described by OpenAPI 3.0.3, at version 1.0.

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

25 operations 13 paths 3 schemas 4 DELETE13 GET4 POST4 PUT

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

Kenjo Organization 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 25

Across 13 paths, the API surfaces 25 operations — 4 DELETE, 13 GET, 4 POST, 4 PUT. Each is listed below with its method, path, parameters, and response codes.

Organization 25

Companies, offices, departments, teams, areas, and calendars.

GET
/companies
List companies
listCompanies → 200401
GET
/offices
List offices
listOffices → 200401
POST
/offices
Create an office
createOffice body → 201401
GET
/offices/{id}
Get an office
getOffice 1 param → 200401404
PUT
/offices/{id}
Update an office
updateOffice 1 param body → 200401
DELETE
/offices/{id}
Delete an office
deleteOffice 1 param → 204401
GET
/departments
List departments
listDepartments → 200401
POST
/departments
Create a department
createDepartment body → 201401
GET
/departments/{id}
Get a department
getDepartment 1 param → 200401404
PUT
/departments/{id}
Update a department
updateDepartment 1 param body → 200401
DELETE
/departments/{id}
Delete a department
deleteDepartment 1 param → 204401
GET
/teams
List teams
listTeams → 200401
POST
/teams
Create a team
createTeam body → 201401
GET
/teams/{id}
Get a team
getTeam 1 param → 200401404
PUT
/teams/{id}
Update a team
updateTeam 1 param body → 200401
DELETE
/teams/{id}
Delete a team
deleteTeam 1 param → 204401
GET
/areas
List areas
listAreas → 200401
POST
/areas
Create an area
createArea body → 201401
GET
/areas/{id}
Get an area
getArea 1 param → 200401404
PUT
/areas/{id}
Update an area
updateArea 1 param body → 200401
DELETE
/areas/{id}
Delete an area
deleteArea 1 param → 204401
GET
/calendars
List calendars
listCalendars → 200401
GET
/calendars/{id}
Get a calendar
getCalendar 1 param → 200401404
GET
/custom-fields
List custom fields
listCustomFields → 200401
GET
/work-schedules/contracted-weekly-minutes
List contracted weekly minutes
listContractedWeeklyMinutes → 200401

Schemas 3

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

Error
object
2 properties
NamedResourceInput
object
1 property 1 required
GenericList
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

kenjo-organization-api-openapi.yml Raw ↑

Other APIs Kenjo publishes across the network.

Kenjo Attendance API
Kenjo Authentication API
Kenjo Compensation API
Kenjo Documents API
Kenjo Employees API
Kenjo Recruiting API
Kenjo Time Off API