Timetracker In Timetracker API
Official vendor OpenAPI document · agent-readyProductivityTask ManagementapiKey, bearer10 EndpointsREST
For Agents
Programmatically health check, validate bearer token. Covers 10 operations with apiKey, bearer authentication.
Use for: I need to health check, I want to validate bearer token, Search for a client, Find all clients
Not supported: Does not handle payments, communications, or crm - use for productivity only.
Time tracking API for managing workspaces, clients, projects, tags, tasks, time entries, and webhook subscriptions. The API exposes 10 endpoints secured with apiKey, bearer authentication.
Install Jentic One Beta
Connect the Timetracker API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Timetracker API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftimetracker.in%2Ftimetracker" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftimetracker.in%2Ftimetracker" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Timetracker API.
Health check
Validate bearer token
Create a client
List clients
Get clients fallback data
Use Cases
Patterns agents use Timetracker API for, with concrete tasks.
★ Productivity Operations
Use the Timetracker API to perform productivity operations programmatically. The API provides 10 endpoints covering core functionality including health check, validate bearer token, create a client.
Call GET /api/health to health check
Automated Auth Management
Automate auth operations by combining multiple Timetracker API endpoints. Agents can validate bearer token and then create a client in a single workflow.
Call GET /api/integrations/zapier/auth to validate bearer token, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Timetracker 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, bearer tokens manually.
Search Jentic for 'health check', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
10 endpoints — time tracking api for managing workspaces, clients, projects, tags, tasks, time entries, and webhook subscriptions.
METHOD
PATH
DESCRIPTION
GET
/api/health
Health check
GET
/api/integrations/zapier/auth
Validate bearer token
POST
/api/integrations/zapier/triggers/clients
Create a client
GET
/api/integrations/zapier/triggers/clients
List clients
GET
/api/integrations/zapier/triggers/clients/fallback
Get clients fallback data
POST
/api/integrations/zapier/actions/tags
Create a tag
GET
/api/integrations/zapier/actions/tags
List tags
POST
/api/integrations/zapier/webhooks/subscribe
Create webhook subscription
GET
/api/health
Health check
GET
/api/integrations/zapier/auth
Validate bearer token
POST
/api/integrations/zapier/triggers/clients
Create a client
GET
/api/integrations/zapier/triggers/clients
List clients
GET
/api/integrations/zapier/triggers/clients/fallback
Get clients fallback data
POST
/api/integrations/zapier/actions/tags
Create a tag
GET
/api/integrations/zapier/actions/tags
List tags
POST
/api/integrations/zapier/webhooks/subscribe
Create webhook subscription
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Timetracker API by hand means choosing between its API-key request header and bearer token, following the Zapier trigger and action endpoints, and handling retries yourself. Through Jentic you install once, import Timetracker from the API Directory, store the credential once, and your agent calls it.
Permission scoping
Timetracker exposes Zapier-style triggers and actions selected by the request body rather than a resource id in the URL path, so scope the agent by the operations it needs, such as reading client triggers or adding tags. You choose that set, so actions like subscribing a webhook are only available if you include them.
Credential isolation
Your Timetracker credential 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.
Intent-based discovery
Agents search Jentic by intent such as 'list new clients' or 'add a tag', and Jentic returns the matching Timetracker operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Timetracker API through Jentic.
What authentication does the Timetracker API use?
The Timetracker API uses apiKey, bearer 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 health check with the Timetracker API?
Yes. Use the GET /api/health endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Timetracker 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 health check through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'health check'. Jentic returns the matching Timetracker API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Timetracker API have?
The Timetracker API exposes 10 endpoints covering auth, clients, system operations.
Can I limit what my agent is allowed to do with the Timetracker API?
Yes. Jentic One is self-hosted by you, so your own rules decide which Timetracker operations and credentials the agent may use. Because Timetracker exposes Zapier-style triggers and actions selected by the request body rather than a resource id in the URL path, you scope the agent to only the operations it needs, such as listing client triggers or creating tags. Higher-impact operations like subscribing a webhook are available only if you choose to include them.
GET STARTED