TimeCamp API

Name: TimeCamp API
Brand: TimeCamp API
Availability: InStock

✓ Official Vendor SpecIdentity AuthAuthorizationbearer, openIdConnect137 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the TimeCamp API to your agent

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

Get information about running timer

Merge time entries

Update group

Create group

GET STARTED

Start building with TimeCamp API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use TimeCamp API for, with concrete tasks.

★ 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.

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.

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.

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

Key Endpoints

137 endpoints — documentation for the timecamp system.

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

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

Why Jentic?

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

Credential isolation

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.

Intent-based discovery

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.

Time to first call

FAQs

Specific to using TimeCamp API through Jentic.

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.

TimeCamp API

Connect the TimeCamp API to your agent

Capabilities

Start building with TimeCamp API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs