Kenjo Rate Limits
Kenjo does not publish fixed numeric rate limits for its REST API in the public reference. Practical throughput is governed by the gated access model rather than by an advertised per-minute request cap: the API is a Connect-plan capability that must be activated per account (sandbox or production) by Kenjo Customer Success, and every request must carry a valid bearer token obtained from POST /auth/login. A missing, invalid, or expired token returns 401 UNAUTHORIZED. Bulk reads (employees, attendances, expected-time, documents, time-off requests) are paginated, so large syncs should page through results and apply client-side backoff.
Kenjo Rate Limits is the machine-readable rate-limit profile for Kenjo on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring requests, items, and bearer token.
The profile also includes 3 backoff/retry policies defined and response codes documented for unauthorized and throttled.
Tagged areas include Human Resources, HRIS, Employee Management, Rate Limiting, and Quotas.