canonical: https://jentic.com/apis/timekit.io/timekit

# Timekit API

Timekit is a scheduling infrastructure platform. The API provides management of resources, availability, bookings, projects, locations, services, reservations, and email templates. The API exposes 47 endpoints secured with basic authentication.

## For AI agents

Programmatically create a resource, list all resources. Covers 47 operations with basic authentication.

## Scope

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

## Capabilities

- Create a resource
- List all resources
- Get a resource
- Update a resource
- Delete a resource
- Query available time slots

## Use cases

### E-Commerce Operations

Use the Timekit API to perform e commerce operations programmatically. The API provides 47 endpoints covering core functionality including create a resource, list all resources, get a resource.

Example prompt: Call POST /resources to create a resource

### Automated App Management

Automate app operations by combining multiple Timekit API endpoints. Agents can list all resources and then get a resource in a single workflow.

Example prompt: Call GET /resources to list all resources, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Timekit 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 basic tokens manually.

Example prompt: Search Jentic for 'create a resource', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/resources` | Create a resource |
| GET | `/resources` | List all resources |
| GET | `/resources/{id}` | Get a resource |
| PUT | `/resources/{id}` | Update a resource |
| DELETE | `/resources/{id}` | Delete a resource |
| POST | `/availability` | Query available time slots |
| POST | `/availability/dates` | Get available dates |
| POST | `/availability/count` | Get availability count |

## Key resources

- **App** — Operations related to App
- **Availability** — Operations related to Availability
- **Bookings** — Operations related to Bookings
- **Email Templates** — Operations related to Email Templates
- **Locations** — Operations related to Locations

## Why Jentic

- **Setup:** Wiring the Timekit API by hand means encoding its basic auth credentials, working through its resource and availability endpoints, and handling retries yourself. Through Jentic you install once, import Timekit from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** Timekit puts the resource id in the URL path (`/resources/{id}`), so a rule can pin your agent to one resource: it can read and update that resource and nothing else. You choose the operations it may call, so a destructive one like resource deletion is not included unless you add it.
- **Credential handling:** Your Timekit 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 'find available times' or 'update a bookable resource', and Jentic returns the matching Timekit 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 Timekit API use?

The Timekit API uses HTTP Basic authentication with username and password. 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 create a resource with the Timekit API?

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

### What are the rate limits for the Timekit 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 create a resource through Jentic?

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

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

The Timekit API exposes 47 endpoints covering app, availability, bookings operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Timekit operations and credentials the agent may use. Since Timekit puts the resource id in the URL path (`/resources/{id}`), a rule can pin the agent to a single resource so it can read and update that one resource and nothing else. You choose the operations it may call, so a destructive action like DELETE `/resources/{id}` stays off limits unless you explicitly grant it.