canonical: https://jentic.com/apis/api.timesheet.io/timesheet

# Timesheet API

The Timesheet API tracks time across projects, tasks, and teams, recording timers, expenses, and notes against each. It manages projects, tasks, tags, rates, and organizations, generates exports and invoice series from tracked time, and drives automations and webhooks, so an agent can run time tracking and billing workflows without manual entry.

## For AI agents

Track time across projects and tasks with timers, expenses, and notes. Manage projects, tasks, tags, rates, teams, and organizations, and generate exports and invoice series from tracked time.

## Scope

Does not handle payroll runs, payment processing, or HR records. Use for time tracking, expenses, and billing exports only.

## Capabilities

- Start, pause, and read the running timer for time tracking
- Manage projects, tasks, and tags that time is tracked against
- Record expenses and notes tied to work
- Manage teams, organizations, and their members
- Generate exports and invoice series from tracked time
- Configure automations, webhooks, and API keys

## Use cases

### Time Tracking Agent

An AI agent records work by starting and stopping the timer against the right task, and logs expenses or notes as they come up. Through Jentic the agent discovers the timer and task operations by intent and calls them directly, so time is captured as work happens without a person opening a tracker.

Example prompt: Start the timer for a task and log an expense against the same project

### Project and Task Setup

Set up the structure that time is tracked against by creating projects, tasks, and tags, and assigning rates. This lets an agent onboard a new client or engagement so that subsequent time entries and invoices map to the right work.

Example prompt: Create a project with a task and apply the billing rate for the engagement

### Billing and Export

Turn tracked time into billing by generating exports and invoice series from the recorded entries. The agent can produce a data export for reporting or an invoice series for a client, closing the loop from tracked time to billing.

Example prompt: Generate an invoice series from the time tracked against a project this month

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/tasks` | List tasks |
| POST | `/v1/tasks` | Create a task |
| GET | `/v1/timer` | Get the running timer |
| GET | `/v1/expenses` | List expenses |
| POST | `/v1/invoice-series` | Create an invoice series |

## Key resources

- **Timers and tasks** — Track time with timers against projects, tasks, and tags
- **Expenses and invoices** — Record expenses and generate exports and invoice series
- **Teams and automations** — Manage teams and organizations and configure automations and webhooks

## Why Jentic

- **Setup:** Wiring the Timesheet API by hand means handling two auth options and the timer, task, and export sequence yourself. Through Jentic you install once, import Timesheet from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Timesheet identifies projects, tasks, and time entries by an id in the request path, so a rule bounds which operations your agent may call. You choose those operations, so destructive ones like deleting a project or an account are not included unless you add them.
- **Credential handling:** Timesheet accepts a JWT bearer token or an API key in the Authorization header. Whichever you provide is stored once, encrypted, by your own Jentic One instance and injected at execution time, so it never enters the agent's prompt or logs.
- **Discovery method:** Agents search Jentic by intent such as 'start a timer' or 'generate an invoice from tracked time', and Jentic returns the matching Timesheet operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Toggl** — Time tracking service compared with Timesheet's timers and projects
- **Clockify** — Free time tracker versus Timesheet's tracking and billing
- **Everhour** — Time tracking that pairs with project tools alongside Timesheet

## FAQ

### What authentication does the Timesheet API use?

The Timesheet API accepts two credentials: a JWT bearer token, or an API key sent in the Authorization header using the ApiKey scheme. Through Jentic whichever you provide is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs.

### Can I start a timer with the Timesheet API?

Yes. Use the timer operations to start, pause, and read the running timer, and GET `/v1/tasks` to pick the task it applies to. Time recorded this way flows into exports and invoice series.

### What are the rate limits for the Timesheet API?

The OpenAPI spec does not specify rate limits. Check the Timesheet documentation at https://api.timesheet.io before running high-volume sync or export jobs.

### Is there a Timesheet MCP server?

You don't need an MCP server to give your agent the Timesheet API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the timer and task operations it needs.

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

Yes. Write a rule that allows only the timer, task, and expense operations, so the agent can track work but cannot delete a project or an account, and every call it makes is logged.

### How do I track time with the Timesheet API through Jentic?

Search Jentic for 'start a timer for a task', and it returns the timer and GET `/v1/tasks` operations with their input schemas so your agent records time directly. To run it on your own infrastructure, install Jentic One from its GitHub repo.