Trackabi API

Name: Trackabi API
Brand: Trackabi API
Availability: InStock

✓ Official Vendor SpecAnalyticsWeb Analyticsbearer19 EndpointsREST

For Agents

Programmatically authenticate user, get initial application state. Covers 19 operations with bearer authentication.

Install Jentic One Beta

Connect the Trackabi API to your agent

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

Authenticate user

Get initial application state

Create user

List all users

GET STARTED

Start building with Trackabi API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Trackabi API for, with concrete tasks.

★ Analytics Operations

Use the Trackabi API to perform analytics operations programmatically. The API provides 19 endpoints covering core functionality including authenticate user, get initial application state, create user.

Call POST /auth/login to authenticate user

Automated auth Management

Automate auth operations by combining multiple Trackabi API endpoints. Agents can get initial application state and then create user in a single workflow.

Call GET /get-initial-state to get initial application state, then verify the result

AI Agent Integration via Jentic

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

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

Key Endpoints

19 endpoints — time tracking and project management api.

METHOD

PATH

DESCRIPTION

POST

/auth/login

Authenticate user

GET

/get-initial-state

Get initial application state

POST

/users

Create user

GET

/users

List all users

GET

/users/{id}

Get user by ID

PUT

/users/{id}

Update user

DELETE

/users/{id}

Delete user

POST

/projects

Create project

POST

/auth/login

Authenticate user

GET

/get-initial-state

Get initial application state

POST

/users

Create user

GET

/users

List all users

GET

/users/{id}

Get user by ID

PUT

/users/{id}

Update user

Why Jentic?

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

Setup

Wiring the Trackabi API by hand means obtaining and sending its bearer token, tracking the trackabi.com/api host, and coding your own request and pagination handling for users and projects. Through Jentic you install once, import the Trackabi API from the API Directory, store the token once, and your agent calls it.

Permission scoping

Trackabi puts the user id in the URL path (/users/{id}), so a rule can pin your agent to a specific user and the operations it needs there. You choose which operations it may call, so destructive ones like deleting a user are not included unless you add them.

Credential isolation

Your Trackabi bearer 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 'authenticate a user' or 'list projects', and Jentic returns the matching Trackabi operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Trackabi API through Jentic.

What authentication does the Trackabi API use?

The Trackabi API uses a Bearer token in the Authorization header. 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 authenticate user with the Trackabi API?

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

What are the rate limits for the Trackabi 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 authenticate user through Jentic?

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

How many endpoints does the Trackabi API have?

The Trackabi API exposes 19 endpoints covering auth, users, projects operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Trackabi operations and credentials the agent may use. Since Trackabi puts the user id in the URL path (/users/{id}), you can pin the agent to a specific user and grant only the operations it needs, such as GET /users/{id} or GET /get-initial-state. Destructive calls like DELETE /users/{id} stay out of reach unless you explicitly allow them.

Trackabi API

Connect the Trackabi API to your agent

Capabilities

Start building with Trackabi API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs