TimeCamp API
✓ Official Vendor SpecIdentity AuthAuthorizationbearer, openIdConnect137 EndpointsREST
For Agents
Programmatically get information about running timer, merge time entries. Covers 137 operations with bearer, openIdConnect authentication.
Use for: I need to information about running timer, I want to merge time entries, Search for time entries changes, Find all time entries deletions
Not supported: Does not handle payments, communications, or crm — use for identity and authentication only.
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.
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.
1
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 | sh2
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 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 TimeCamp API.
Get information about running timer
Merge time entries
Update group
Create group
Monitor TimeCamp API operational status and events
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
/group
Get all groups
PUT
/group
Create group
DELETE
/group
Delete group
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
TimeCamp API bearer, openIdConnect credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'get information about running timer') and Jentic returns the matching TimeCamp API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct TimeCamp API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.
GET STARTED