Install Jentic One Beta

Connect the Toggl Track API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Toggl Track 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftoggl.com%2Ftoggl" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftoggl.com%2Ftoggl" | 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 Toggl Track API.

Get current user

Update current user

List my time entries

Query and filter Toggl Track API records by parameters

GET STARTED

Start building with Toggl Track API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Toggl Track API for, with concrete tasks.

★ Analytics Operations

Use the Toggl Track API to perform analytics operations programmatically. The API provides 31 endpoints covering core functionality including get current user, update current user, list my time entries.

Call GET /me to get current user

Automated Clients Management

Automate clients operations by combining multiple Toggl Track API endpoints. Agents can update current user and then list my time entries in a single workflow.

Call PUT /me to update current user, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Toggl Track 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 basic tokens manually.

Search Jentic for 'get current user', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

31 endpoints — toggl track time tracking api.

METHOD

PATH

DESCRIPTION

GET

/me

Get current user

PUT

/me

Update current user

GET

/me/time_entries

List my time entries

GET

/me/time_entries/current

Get running time entry

GET

/me/projects

List my projects

GET

/me/organizations

List my organizations

GET

/workspaces

List workspaces

GET

/workspaces/{workspace_id}

Get workspace

GET

/me

Get current user

PUT

/me

Update current user

GET

/me/time_entries

List my time entries

GET

/me/time_entries/current

Get running time entry

GET

/me/projects

List my projects

GET

/me/organizations

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Toggl Track API by hand means encoding its basic auth credentials, threading the workspace id through most paths, and handling retries yourself. Through Jentic you install once, import Toggl Track from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

Toggl Track puts the workspace id in the URL path (/workspaces/{workspace_id}/...), so a rule can pin your agent to one workspace: it works within that workspace and nothing else. You choose the operations it may call, so destructive ones like deleting a time entry or project are not included unless you add them.

Credential isolation

Your Toggl Track credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list my time entries' or 'create a project in a workspace', and Jentic returns the matching Toggl Track operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Toggl Track API through Jentic.

What authentication does the Toggl Track API use?

The Toggl Track API uses HTTP Basic authentication with username and password. 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 current user with the Toggl Track API?

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

What are the rate limits for the Toggl Track 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 current user through Jentic?

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

How many endpoints does the Toggl Track API have?

The Toggl Track API exposes 31 endpoints covering clients, groups, organizations operations.

Can I limit what my agent is allowed to do with the Toggl Track API?

Yes. Because you self-host Jentic One, your own rules decide which Toggl Track operations and credentials the agent may use. Since Toggl Track carries the workspace id in the URL path (/workspaces/{workspace_id}/...), a rule can pin the agent to a single workspace so it never touches others. You also choose the exact operations it can call, so destructive ones like deleting a time entry or a project stay off unless you add them.

Toggl Track API

Name: Toggl Track API
Brand: Toggl Track API
Availability: InStock

Official vendor OpenAPI document · agent-readyAnalyticsWeb Analyticsbasic31 EndpointsREST

For Agents

Programmatically get current user, update current user. Covers 31 operations with basic authentication.

Use for: I need to current user, I want to current user, Search for my time entries, Find all running time entry

Not supported: Does not handle payments, communications, or crm - use for analytics only.

Toggl Track time tracking API. Manage time entries, projects, clients, tags, and reports. The API exposes 31 endpoints secured with basic authentication.

Jentic One on Github View OpenAPI Document

Connect the Toggl Track API to your agent

Capabilities

Start building with Toggl Track API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Toggl Track API