Kenjo · Rate Limits

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, in the API Commons Rate Limits shape.

It captures 3 rate-limit definitions, measuring requests, items, and bearer token.

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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.

3 Limits Exhausted: HTTP 429
Method: generated, dated 2026-07-11.
Written by API Evangelist on 2026-07-11 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Human ResourcesHRISEmployee ManagementRate LimitingQuotas

Limits

REST API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the Kenjo API.
Pagination endpoint
items
configurable via page and limit
List endpoints are paginated; page through large result sets rather than requesting everything at once.
Token Validity token
bearer token
expires
Bearer tokens from POST /auth/login expire; an expired token returns 401 and must be re-issued.

Policies

Entitlement Gating
API access is a Connect-plan capability activated per account by Kenjo Customer Success, which bounds who can call the API before any rate limit applies.
Authentication Required
Every request must include a valid bearer token in the Authorization header; missing/invalid/expired tokens return 401 UNAUTHORIZED.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After if a 429 is returned.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/kenjo-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.