Install Jentic One Beta

Connect the Tick Time Tracking to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Tick Time Tracking, 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%2Ftickspot.com%2Ftickspot" | 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%2Ftickspot.com%2Ftickspot" | 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 Tick Time Tracking API.

List roles and API tokens for authenticated user

Create a new client (admin only)

Get a specific client

Update a client (admin only)

Delete a client (admin only, no projects)

GET STARTED

Start building with Tick Time Tracking API

Explore with Jentic One

View OpenAPI Document

Automated Clients Management

Automate clients operations by combining multiple Tick Time Tracking endpoints. Agents can create a new client (admin only) and then list clients with projects in a single workflow.

Call POST /clients.json to create a new client (admin only), then verify the result

AI Agent Integration via Jentic

AI agents discover and call Tick Time Tracking 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 apiKey, basic tokens manually.

Search Jentic for 'list roles and API tokens for authenticated user', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

33 endpoints — tick time tracking api for managing clients, projects, tasks, time entries, and users.

METHOD

PATH

DESCRIPTION

GET

/roles.json

List roles and API tokens for authenticated user

POST

/clients.json

Create a new client (admin only)

GET

/clients.json

List clients with projects

GET

/clients/all.json

List all clients including those without projects

GET

/clients/{client_id}.json

Get a specific client

PUT

/clients/{client_id}.json

Update a client (admin only)

DELETE

/clients/{client_id}.json

Delete a client (admin only, no projects)

POST

/projects.json

Create a new project (admin only)

GET

/roles.json

List roles and API tokens for authenticated user

POST

/clients.json

Create a new client (admin only)

GET

/clients.json

List clients with projects

GET

/clients/all.json

List all clients including those without projects

GET

/clients/{client_id}.json

Get a specific client

PUT

/clients/{client_id}.json

Update a client (admin only)

DELETE

/clients/{client_id}.json

Delete a client (admin only, no projects)

POST

/projects.json

Create a new project (admin only)

Why Jentic?

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

Setup

Wiring the Tick Time Tracking API by hand means choosing between its Token header auth and basic auth, filling in your {subscription_id} in the host, and building the client and project calls yourself. Through Jentic you install once, import Tick Time Tracking from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Tick puts the client id in the URL path (/clients/{client_id}.json), so a rule can pin your agent to one client: it can read that client and nothing else. You choose the operations it may call, so destructive ones like updating or deleting a client are not included unless you add them.

Credential isolation

Your Tick Time Tracking credential 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 'list clients' or 'create a project', and Jentic returns the matching Tick Time Tracking operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Tick Time Tracking API through Jentic.

What authentication does the Tick Time Tracking use?

The Tick Time Tracking uses apiKey, basic 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 list roles and API tokens for authenticated user with the Tick Time Tracking?

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

What are the rate limits for the Tick Time Tracking?

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 list roles and API tokens for authenticated user through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list roles and API tokens for authenticated user'. Jentic returns the matching Tick Time Tracking operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Tick Time Tracking have?

The Tick Time Tracking exposes 33 endpoints covering clients, clients.json, entries operations.

Can I limit what my agent is allowed to do with the Tick Time Tracking API?

Yes. Because you run Jentic One yourself, your own rules decide which Tick operations and credentials the agent can use. Since Tick puts the client id in the URL path (/clients/{client_id}.json), you can pin the agent to a single client so it only reads that client and nothing else. You also choose the operations it may call, so destructive ones like PUT /clients/{client_id}.json or DELETE /clients/{client_id}.json stay off the list unless you explicitly add them.

Tickspot Tick Time Tracking

Name: Tick Time Tracking API
Brand: Tick Time Tracking
Availability: InStock

Community OpenAPI document · agent-readyAnalyticsWeb AnalyticsapiKey, basic33 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Programmatically list roles and API tokens for authenticated user, create a new client (admin only). Covers 33 operations with apiKey, basic authentication.

Use for: I need to roles and API tokens for authenticated user, I want to a new client (admin only), Search for clients with projects, Find all all clients including those without projects

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

Tick time tracking API for managing clients, projects, tasks, time entries, and users. The API exposes 33 endpoints secured with apiKey, basic authentication.

Jentic One on Github View OpenAPI Document

Connect the Tick Time Tracking to your agent

Capabilities

Start building with Tick Time Tracking API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Tickspot Tick Time Tracking