canonical: https://jentic.com/apis/timeetc.co.uk/timeetc

# Time etc API

Time etc virtual assistant platform API for task management, comments, and team operations. The API exposes 7 endpoints secured with apiKey authentication.

## For AI agents

Programmatically login and get auth token, get tasks created in last 15 minutes. Covers 7 operations with apiKey authentication.

## Scope

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

## Capabilities

- Login and get auth token
- Get tasks created in last 15 minutes
- Create a new task
- Query and filter Time etc API records by parameters
- Monitor Time etc API operational status and events

## Use cases

### Productivity Operations

Use the Time etc API to perform productivity operations programmatically. The API provides 7 endpoints covering core functionality including login and get auth token, get tasks created in last 15 minutes, create a new task.

Example prompt: Call POST `/authorization/zapier` to login and get auth token

### Automated Authentication Management

Automate authentication operations by combining multiple Time etc API endpoints. Agents can get tasks created in last 15 minutes and then create a new task in a single workflow.

Example prompt: Call GET `/zapier/new-tasks` to get tasks created in last 15 minutes, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Time etc 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 apiKey tokens manually.

Example prompt: Search Jentic for 'login and get auth token', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/authorization/zapier` | Login and get auth token |
| GET | `/zapier/new-tasks` | Get tasks created in last 15 minutes |
| POST | `/zapier/create-new-task` | Create a new task |
| GET | `/zapier/new-comments` | Get comments created in last 15 minutes |
| GET | `/zapier/logged-times` | Get logged times in last 15 minutes |
| GET | `/zapier/completed-tasks` | Get tasks completed in last 15 minutes |
| GET | `/zapier/team` | Get all assistants in team |

## Key resources

- **Authentication** — Operations related to Authentication
- **Tasks** — Operations related to Tasks
- **Comments** — Operations related to Comments
- **Time Tracking** — Operations related to Time Tracking
- **Team** — Operations related to Team

## Why Jentic

- **Setup:** Wiring the Time etc API by hand means setting its X-Auth-Token header, following the Zapier-style task and comment endpoints, and handling retries yourself. Through Jentic you install once, import Time etc from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Time etc addresses tasks and comments through the request body rather than the URL path, so scope the agent by the operations it needs, such as listing new tasks or creating a task. You choose that set, so operations you do not name stay unavailable.
- **Credential handling:** Your Time etc token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list new tasks' or 'log a completed task', and Jentic returns the matching Time etc operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Asana** — Alternative productivity API
- **Monday** — Alternative productivity API
- **Clickup** — Complementary productivity API

## FAQ

### What authentication does the Time etc API use?

The Time etc API uses an API key passed in the `X-Auth-Token` header. 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 login and get auth token with the Time etc API?

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

### What are the rate limits for the Time etc 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 login and get auth token through Jentic?

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

### How many endpoints does the Time etc API have?

The Time etc API exposes 7 endpoints covering authentication, tasks, comments operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Time etc operations and credentials the agent may use, so you can allow only the calls it needs, such as listing new tasks or creating a task, while withholding others like reading comments, logged times, completed tasks, or the team roster. Time etc addresses tasks and comments through the request body rather than the URL path, so you scope the agent by the specific operations you name rather than by path patterns. Any operation you do not grant stays unavailable to the agent, and your stored token is injected only for the calls you allow.