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 Attendance API

Attendance and time-tracking entries.

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

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

This API exposes 8 operations across 5 paths, and defines 6 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.

8 operations 5 paths 6 schemas 1 DELETE4 GET2 POST1 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 Attendance 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 8

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

Attendance 8

Attendance and time-tracking entries.

GET
/attendances
List attendances
listAttendances 2 params → 200401
POST
/attendances
Create an attendance
createAttendance body → 201401
GET
/attendances/{attendanceId}
Get an attendance
getAttendance 1 param → 200401404
PUT
/attendances/{attendanceId}
Update an attendance
updateAttendance 1 param body → 200401
DELETE
/attendances/{attendanceId}
Delete an attendance
deleteAttendance 1 param → 204401
POST
/attendances/track-time
Track an attendance entry
trackTime body → 200401
GET
/attendances/categories
List attendance categories
listAttendanceCategories → 200401
GET
/attendances/expected-time
List expected time per user
listExpectedTime 2 params → 200401

Schemas 6

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

GenericList
object
4 properties
Attendance
AttendanceList
Error
object
2 properties
TrackTimeInput
object
4 properties 1 required
AttendanceInput
object
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

kenjo-attendance-api-openapi.yml Raw ↑

Other APIs Kenjo publishes across the network.

Kenjo Authentication API
Kenjo Compensation API
Kenjo Documents API
Kenjo Employees 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 Attendance 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.