canonical: https://jentic.com/apis/timecamp.com/timecamp

# TimeCamp API

Documentation for the TimeCamp system. Get your API token here: https://app.timecamp.com/app#/settings/users/me Be aware that you can reach API calls limit. Once you do you will get HTTP code 429 response. Request example:. The API exposes 137 endpoints secured with bearer, openIdConnect authentication.

## For AI agents

Programmatically get information about running timer, merge time entries. Covers 137 operations with bearer, openIdConnect authentication.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- Get information about running timer
- Merge time entries
- Update group
- Create group
- Monitor TimeCamp API operational status and events

## Use cases

### Identity and Authentication Operations

Use the TimeCamp API to perform identity auth operations programmatically. The API provides 137 endpoints covering core functionality including get information about running timer, merge time entries, get time entries changes.

Example prompt: Call GET /timer_running to get information about running timer

### Automated [v1] User Management

Automate [v1] user operations by combining multiple TimeCamp API endpoints. Agents can merge time entries and then get time entries changes in a single workflow.

Example prompt: Call POST /entries_merge to merge time entries, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call TimeCamp 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 bearer, openIdConnect tokens manually.

Example prompt: Search Jentic for 'get information about running timer', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /timer_running | Get information about running timer |
| POST | /entries_merge | Merge time entries |
| GET | /entries_changes | Get time entries changes |
| GET | /entries_deletions | Get time entries deletions |
| POST | /group | Update group |
| GET | /group | Get all groups |
| PUT | /group | Create group |
| DELETE | /group | Delete group |

## Key resources

- **[v1] User** — Operations related to [v1] User
- **[v1] Entry** — Operations related to [v1] Entry
- **[v1] Tags** — Operations related to [v1] Tags
- **[v1] Group** — Operations related to [v1] Group
- **[v1] Approvals** — Operations related to [v1] Approvals

## Why Jentic

- **Setup:** Wiring the TimeCamp API by hand means handling its bearer token, choosing between the app.timecamp.com/third_party/api host and the v4.api.timecamp.com host, and managing your own retries against 137 endpoints. Through Jentic you install once, import TimeCamp from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** TimeCamp identifies timers, entries, and groups through the request body rather than the URL path, so scope the agent by the operations it needs, such as reading a running timer or merging entries. You choose that set, so operations like deleting a group stay out unless you add them.
- **Credential handling:** Your TimeCamp 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 'check if a timer is running' or 'list changed time entries', and Jentic returns the matching TimeCamp operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the TimeCamp API use?

The TimeCamp API uses bearer, openIdConnect 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 get information about running timer with the TimeCamp API?

Yes. Use the GET /timer_running endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the TimeCamp 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 get information about running timer through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get information about running timer'. Jentic returns the matching TimeCamp API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the TimeCamp API have?

The TimeCamp API exposes 137 endpoints covering [v1] user, [v1] entry, [v1] tags operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which TimeCamp operations and credentials the agent can use. Because TimeCamp identifies timers, entries, and groups through the request body rather than the URL path, you scope the agent to the operations it needs, such as reading a running timer with GET /timer_running or merging entries with POST /entries_merge. Operations you do not grant, like deleting a group with DELETE /group, stay out of reach until you add them.