Everhour Time Tracking API

Name: Everhour Time Tracking API
Brand: Everhour Time Tracking API
Availability: InStock

✓ Official Vendor SpecProductivityTask ManagementapiKey40 EndpointsREST

For Agents

Manage Everhour clients, invoices, expenses, projects, tasks, and time records, and post or correct time entries on behalf of users.

Install Jentic One Beta

Connect the Everhour Time Tracking API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Everhour Time Tracking 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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Everhour Time Tracking API.

Manage clients and per-client budgets via the /clients endpoints

Create, send, and update invoices including expense line items

Track expenses by project and reconcile them against time records

GET STARTED

Start building with Everhour Time Tracking API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Everhour Time Tracking API for, with concrete tasks.

★ Time-to-Invoice Sync

Mirror Everhour time records and expenses into the accounting system so monthly invoicing is driven by actual tracked hours rather than manual exports. The /invoices, /expenses, and /time endpoints provide the structured data, and the per-client invoice endpoints let automation create, update, and finalise invoices. A working sync takes 1-2 days and saves finance teams hours per month.

For each client, pull /clients/{client_id}/invoices for the current period, plus matching /expenses, and post a draft invoice into the connected accounting tool

Project Budget Monitoring

Run a daily check that compares logged time against project budgets so project managers are warned before a project goes over. The /projects and /clients/{client_id}/budget endpoints expose the budget structure, and the /time and /tasks endpoints provide the actuals. Reports are produced in seconds per project.

For every active project, sum tracked /time hours and post a Slack alert if the project is at or above 80 percent of its budget

Capacity and Resource Planning

Power a capacity dashboard by combining timecards, timesheets, and resource planning data so leaders can see who is over-committed and where there is slack. The Everhour API exposes all three resources, and the data refreshes in seconds. This replaces manual spreadsheet planning.

Pull this week's timesheets and resource plans and post the names of the three people most over their target utilisation to the leadership channel

AI Agent Integration via Jentic

Connect Everhour to an AI assistant through Jentic so team members can post time records, check budgets, or run reports in chat. Jentic search resolves natural-language intents to the right Everhour operation and the vault holds the API key. Setup takes minutes once Everhour is connected.

Search Jentic for 'log everhour time entry', load the POST /time operation, and post '2 hours on task_123 today' captured from chat

Key Endpoints

40 endpoints — the everhour api is the programmatic surface for the everhour time tracking and project budgeting platform.

METHOD

PATH

DESCRIPTION

GET

/clients

List clients

POST

/clients

Create a client

GET

/projects

List projects

GET

/projects/{project_id}/tasks

List tasks in a project

GET

/tasks/search

Search tasks

POST

/time

Post a time record

GET

/invoices

List invoices

POST

/expenses

Post an expense

GET

/clients

List clients

POST

/clients

Create a client

GET

/projects

List projects

GET

/projects/{project_id}/tasks

List tasks in a project

GET

/tasks/search

Search tasks

POST

/time

Post a time record

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Everhour API key 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 an everhour time entry' or 'search tasks', and Jentic returns the matching Everhour operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Everhour Time Tracking API through Jentic.

What authentication does the Everhour API use?

The Everhour API uses an API key (apiKeyAuth scheme). Through Jentic, the key is stored in the encrypted vault and injected at execution time, so it never appears in the agent's prompt or in logs.

Can I post time records through the Everhour API?

Yes. POST /time creates a new time record, PUT /time/{time_id} updates an existing one, and DELETE /time/{time_id} removes it. This is the right surface for chat-based time logging or downstream sync from another tool.

What are the rate limits for the Everhour API?

The OpenAPI spec does not declare explicit rate limits. Treat the API as standard for SaaS and back off on HTTP 429; consult Everhour developer documentation for current published limits before bulk syncs.

How do I create an invoice through Jentic?

Search Jentic for 'everhour create invoice', load the POST /clients/{client_id}/invoices operation, and execute it with the line items. Install with pip install jentic and use the async search, load, execute pattern.

Does the Everhour API support project budgets?

Yes. PUT /clients/{client_id}/budget sets a client-level budget and DELETE /clients/{client_id}/budget removes it. Combine with /projects and /time to monitor burn rate over the budget.

Can I search tasks across all projects?

Yes. GET /tasks/search returns tasks matching a query string, which is faster than listing every project's tasks individually when looking for a specific work item.

Can I limit what my agent is allowed to do with the Everhour Time Tracking API?

Yes. Because Jentic One is self-hosted, you decide which Everhour operations your agent may call, and it can only use the set you allow. You might permit posting a time record with POST /time and reading projects with GET /projects while withholding invoice or expense operations such as POST /clients/{client_id}/invoices or POST /expenses. Note that Everhour puts the project id in the path for task reads like GET /projects/{project_id}/tasks but takes time entries and expenses in the request body, so you scope the agent by the operations it needs rather than by a single record, and it uses your stored key only for those calls.

Everhour Time Tracking API

Connect the Everhour Time Tracking API to your agent

Capabilities

Start building with Everhour Time Tracking API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs