canonical: https://jentic.com/apis/sandbox-api.kenjo.io/sandbox-api-kenjo

# Sandbox Api Kenjo Kenjo API

Before starting to use the Kenjo API, you have to request the API activation for a sandbox or production environment to the Kenjo Customer Success team. After that, an admin user has to go to *Settings > Integrations > API keys*, to generate the **API Key**. Follow the steps described in the **Autentication section** of this document. <br>The API key is needed to request the bearer token. Each end. The API exposes 62 endpoints.

## For AI agents

Programmatically log in an API token., log out an API token.. Covers 62 operations.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- Log in an API token.
- Return an attendance for a given attendance id.
- Update an attendance for a given attendance id.
- Delete an attendance for a given attendance id.
- Create a new attendance.

## Use cases

### E-Commerce Operations

Use the Kenjo API to perform e commerce operations programmatically. The API provides 62 endpoints covering core functionality including log in an API token., log out an API token., return an attendance for a given attendance id..

Example prompt: Call POST `/auth/login` to log in an API token.

### Automated Employees Management

Automate employees operations by combining multiple Kenjo API endpoints. Agents can log out an API token. and then return an attendance for a given attendance id. in a single workflow.

Example prompt: Call POST `/auth/logout` to log out an API token., then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Kenjo API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'log in an API token.', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/auth/login` | Log in an API token. |
| POST | `/auth/logout` | Log out an API token. |
| GET | `/attendances/{attendanceId}` | Return an attendance for a given attendance id. |
| PUT | `/attendances/{attendanceId}` | Update an attendance for a given attendance id. |
| DELETE | `/attendances/{attendanceId}` | Delete an attendance for a given attendance id. |
| POST | `/attendances` | Create a new attendance. |
| GET | `/attendances` | Return a list of attendances. |
| POST | `/attendances/track-time` | Track an attendance entry. |

## Key resources

- **Employees** — Operations to manage employees in Kenjo.
- **Attendance** — Operations to manage attendance entries related to employees.
- **Offices** — Operations to manage offices in Kenjo.
- **Departments** — Operations to manage departments in Kenjo.
- **Teams** — Operations to manage teams in Kenjo.

## Why Jentic

- **Setup:** Wiring the Kenjo API by hand means logging in for a token, pointing requests at the sandbox or production kenjo.io host, and handling attendance paging and retries yourself. Through Jentic you install once, import Kenjo from the API Directory, store the login credentials once, and your agent calls it.
- **Permission scoping:** Kenjo puts the record id in the URL path (`/attendances/{attendanceId}`), so a rule can pin your agent to specific attendance records: it can read or update the ones you allow and nothing else. You choose the operations it may call, so actions like deleting an attendance are not included unless you add them.
- **Credential handling:** Your Kenjo credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'log in to get a token' or 'track time on an attendance', and Jentic returns the matching Kenjo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### What authentication does the Kenjo API use?

The Kenjo API uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I log in an API token. with the Kenjo API?

Yes. Use the POST `/auth/login` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Kenjo API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I log in an API token. through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'log in an API token.'. Jentic returns the matching Kenjo API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Kenjo API have?

The Kenjo API exposes 62 endpoints covering employees, attendance, offices operations.

### Can I limit what my agent is allowed to do with the Kenjo API?

Yes. Because you run Jentic One yourself, your own rules decide which Kenjo operations and credentials the agent may use. Since Kenjo puts the record id in the URL path, such as `/attendances/{attendanceId}`, you can pin the agent to specific attendance records and let it read or update only the ones you allow. You also choose which operations it may call, so an action like DELETE `/attendances/{attendanceId}` stays off limits unless you add it.