ClickTime API
68
AI ReadinessAI-Aware (B+)68/100
Agent-ready OpenAPI document · curated by JenticProductivityTask Managementbearer16 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Log time entries, manage expenses, and read jobs, tasks, clients, and users in ClickTime via a versioned bearer-authenticated REST API.
Use for: Log a time entry against a job for a user, Update an existing ClickTime time entry, Delete a time entry that was logged in error, List all jobs for the company
Not supported: Does not handle creating jobs, tasks, or clients, running invoicing, or executing payroll - use for time entries, expenses, and reading workspace metadata only.
Jentic publishes the only available OpenAPI specification for ClickTime API, keeping it validated and agent-ready. ClickTime is a time-tracking, expense, and project-budgeting platform used by professional services firms to bill clients accurately and forecast capacity. The 1.3 REST surface exposes time entries, expenses, jobs, tasks, clients, users, and the company record so integrators can sync ClickTime data into accounting, project management, or analytics tooling. Authentication uses a bearer token derived from a ClickTime API key.
Install Jentic One Beta
Connect the ClickTime API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ClickTime 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%2Fapp.clicktime.com%2Fclicktime" | 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%2Fapp.clicktime.com%2Fclicktime" | 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 ClickTime API.
Create, retrieve, update, and delete time entries against /companies/{companyId}/users/{userId}/timeentries
Log expenses for a user via POST /companies/{companyId}/users/{userId}/expenses
List a company's jobs, tasks, and clients to drive project picklists
Read user records and the current authenticated user via GET /me
Pull the ClickTime company record for tenant-aware integrations
Use Cases
Patterns agents use ClickTime API for, with concrete tasks.
★ Project Time Tracking from External Tools
Engineering and consulting teams log time from inside Jira, Asana, or Slack rather than the ClickTime UI, so timesheets stay accurate without context switching. POST /companies/{companyId}/users/{userId}/timeentries records the entry against the right job and task, while GET /companies/{companyId}/jobs and GET /companies/{companyId}/tasks back the picklist that the user sees.
Call POST /companies/{companyId}/users/{userId}/timeentries with the userId, jobId, taskId, hours, and date for the work done.
Expense Report Submission
Finance teams replace email attachments with a structured expense submission flow that posts directly to ClickTime. POST /companies/{companyId}/users/{userId}/expenses creates the entry against the user, and GET /companies/{companyId}/users/{userId}/expenses lists submitted items so a manager can review the pending queue.
Submit an expense via POST /companies/{companyId}/users/{userId}/expenses with the amount, category, and date for an out-of-pocket reimbursement.
Project Profitability Reporting
Operations and finance teams pull time entries and combine them with billing rates to produce per-project margin reports. Iterating GET /companies/{companyId}/users with a per-user GET /companies/{companyId}/users/{userId}/timeentries call yields the timesheet feed; jobs and tasks expose the project context needed to attribute the time to the right engagement.
Iterate users via GET /companies/{companyId}/users and pull each user's time entries via GET /companies/{companyId}/users/{userId}/timeentries for the reporting window.
AI Agent Time-Tracking Assistant
An AI assistant that helps a consultant or engineer summarise their week and post timesheets uses Jentic to call ClickTime without managing the bearer token directly. Jentic exposes the time-entry, job, and task endpoints by intent, validates inputs against the schema, and isolates credentials.
Search Jentic for 'log a time entry to ClickTime', load the schema for POST /companies/{companyId}/users/{userId}/timeentries, and execute it with the user's hours for each job for the day.
Key Endpoints
16 endpoints — jentic publishes the only available openapi specification for clicktime api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/me
Get the currently authenticated user.
POST
/companies/{companyId}/users/{userId}/timeentries
Create a time entry for a user.
GET
/companies/{companyId}/users/{userId}/timeentries
List a user's time entries.
PUT
/companies/{companyId}/users/{userId}/timeentries/{timeEntryId}
Update an existing time entry.
DELETE
/companies/{companyId}/users/{userId}/timeentries/{timeEntryId}
Delete a time entry.
POST
/companies/{companyId}/users/{userId}/expenses
Create an expense entry for a user.
GET
/companies/{companyId}/jobs
List jobs for the company.
GET
/companies/{companyId}/tasks
List tasks for the company.
GET
/me
Get the currently authenticated user.
POST
/companies/{companyId}/users/{userId}/timeentries
Create a time entry for a user.
GET
/companies/{companyId}/users/{userId}/timeentries
List a user's time entries.
PUT
/companies/{companyId}/users/{userId}/timeentries/{timeEntryId}
Update an existing time entry.
DELETE
/companies/{companyId}/users/{userId}/timeentries/{timeEntryId}
Delete a time entry.
POST
/companies/{companyId}/users/{userId}/expenses
Create an expense entry for a user.
GET
/companies/{companyId}/jobs
List jobs for the company.
GET
/companies/{companyId}/tasks
List tasks for the company.
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
C
ClickTime API
- AI-Aware (B+)68/100
100
Foundational Compliance63
Developer Experience & Jentic Compatibility47
AI-Readiness & Agent Experience94
Agent Usability60
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
47
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D+Signals: 4
32%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
57%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring ClickTime by hand means learning its bearer auth and threading companyId and userId through every time-entry and expense path yourself. Through Jentic you install once, import the ClickTime API from the API Directory, store the token once, and your agent calls it.
Permission scoping
ClickTime puts the company and user ids in the URL path (/companies/{companyId}/users/{userId}/timeentries/...), so a rule can pin your agent to one user's time entries and expenses in one company. You choose the operations it may call, so destructive ones like deleting a time entry are not included unless you add them.
Credential isolation
Your ClickTime bearer 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.
Intent-based discovery
Agents search Jentic by intent such as 'log a time entry' or 'list all jobs', and Jentic returns the matching ClickTime operation with its path and body schema so the agent calls the right endpoint without reading the ClickTime help reference.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using ClickTime API through Jentic.
Why is there no official OpenAPI spec for ClickTime API?
ClickTime publishes its developer reference as HTML at app.clicktime.com/api/1.3/help. Jentic generates and maintains this spec so that AI agents and developers can call ClickTime API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the ClickTime API use?
ClickTime uses HTTP Bearer authentication - generate an API key from your ClickTime profile and pass it as Authorization: Bearer <token>. Through Jentic the token is stored encrypted in the vault and injected at call time, so it never enters the agent's prompt context.
Can I create new jobs or tasks via the API?
Not in this version. The 1.3 surface exposes GET-only endpoints for /companies/{companyId}/jobs, /companies/{companyId}/tasks, and /companies/{companyId}/clients - useful for picklists but not for provisioning. Job and task creation is performed inside the ClickTime workspace by an administrator.
What are the rate limits for the ClickTime API?
Rate limits are not declared in the OpenAPI spec. ClickTime applies plan-level throttles that surface as 429 responses; treat batch reporting jobs as paginated and cache the results of jobs, tasks, and clients calls rather than re-fetching on every page load.
How do I post a time entry through Jentic?
Run pip install jentic, then search Jentic for 'log a time entry', load the schema for POST /companies/{companyId}/users/{userId}/timeentries, and execute it with the userId, jobId, taskId, hours, and date. Jentic injects the bearer token from your stored ClickTime credentials. Run it through Jentic One, the self-hosted execution layer.
Can the API tell me who the current user is?
Yes. GET /me returns the currently authenticated ClickTime user, which is useful when the same bearer token is shared across tools and the application needs to attribute time to the person who connected the account.
Can I limit what my agent is allowed to do with the ClickTime API?
Yes. Because you run Jentic One yourself, your own rules decide which ClickTime operations and credentials the agent may use. Since ClickTime carries the company and user ids in the URL path, like /companies/{companyId}/users/{userId}/timeentries, you can pin the agent to a single user's time entries and expenses within one company. You also choose the operations it may call, so a destructive one like DELETE /companies/{companyId}/users/{userId}/timeentries/{timeEntryId} is left out unless you explicitly add it.
GET STARTED