canonical: https://jentic.com/apis/trackfront.com/trackfront

# TrackFront V1

trackfront.com/main version 1.0.0. The API exposes 24 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically returns list of contacts by account, returns list of contacts in organization. Covers 24 operations with oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Returns list of contacts by account
- Deletes contact from account
- Create contact
- Update existing contact
- Monitor TrackFront V1 operational status and events

## Use cases

### Developer Tools Operations

Use the TrackFront V1 to perform developer tools operations programmatically. The API provides 24 endpoints covering core functionality including returns list of contacts by account, returns list of contacts in organization, returns list of contacts that match search string.

Example prompt: Call GET `/accounts/contacts` to returns list of contacts by account

### Automated Accounts Management

Automate accounts operations by combining multiple TrackFront V1 endpoints. Agents can returns list of contacts in organization and then returns list of contacts that match search string in a single workflow.

Example prompt: Call GET `/accounts/contacts/{organization_id}` to returns list of contacts in organization, then verify the result

### AI Agent Integration via Jentic

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

Example prompt: Search Jentic for 'returns list of contacts by account', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/accounts/contacts` | Returns list of contacts by account |
| GET | `/accounts/contacts/{organization_id}` | Returns list of contacts in organization |
| GET | `/accounts/contacts/{searchstring}` | Returns list of contacts that match search string |
| GET | `/accounts/contacts/{contact_id}` | Returns contact by id |
| DELETE | `/accounts/contacts/{contact_id}` | Deletes contact from account |
| POST | `/accounts/contact/` | Create contact |
| PUT | `/accounts/contact/` | Update existing contact |
| GET | `/accounts/users` | Returns list of users by account |

## Key resources

- **Accounts** — Operations for accounts
- **Estimates** — Operations for estimates
- **Projects** — Operations for projects
- **Trackings** — Operations for trackings

## Why Jentic

- **Setup:** Wiring TrackFront by hand means running its OAuth2 client-credentials exchange, sending the resulting token, and tracking the app.trackfront.com v1 host across its contact and account routes. Through Jentic you install once, import TrackFront V1 from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** TrackFront puts the contact id in the URL path (`/accounts/contacts/{contact_id}`), so a rule can pin your agent to a specific contact and the operations it needs there. You choose which operations it may call, so destructive ones like deleting a contact are not included unless you add them.
- **Credential handling:** Your TrackFront OAuth2 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.
- **Discovery method:** Agents search Jentic by intent such as 'list contacts by account' or 'get a contact by id', and Jentic returns the matching TrackFront operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the TrackFront V1 use?

The TrackFront V1 uses OAuth 2.0 for authorization. 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 returns list of contacts by account with the TrackFront V1?

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

### What are the rate limits for the TrackFront V1?

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 returns list of contacts by account through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'returns list of contacts by account'. Jentic returns the matching TrackFront V1 operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the TrackFront V1 have?

The TrackFront V1 exposes 24 endpoints covering accounts, estimates, projects operations.

### Can I limit what my agent is allowed to do with the TrackFront V1 API?

Yes. Because you run Jentic One yourself, your own rules decide which TrackFront operations and credentials the agent may use. TrackFront puts the contact id in the URL path (`/accounts/contacts/{contact_id}`), so you can pin the agent to a specific contact and only the read operations it needs there, such as GET `/accounts/contacts.` You choose which operations are exposed, so destructive calls like DELETE `/accounts/contacts/{contact_id}` stay out of reach unless you explicitly allow them.