canonical: https://jentic.com/apis/timelink.io/timelink

# timelink API

Sync your clients, projects and services or track your time with the timelink API. The API exposes 39 endpoints secured with bearer authentication.

## For AI agents

Programmatically get token details, create client. Covers 39 operations with bearer authentication.

## Scope

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

## Capabilities

- Get token details
- Create client
- List clients
- Search clients
- Update client
- Partially update client

## Use cases

### Developer Tools Operations

Use the timelink API to perform developer tools operations programmatically. The API provides 39 endpoints covering core functionality including get token details, create client, list clients.

Example prompt: Call GET /token to get token details

### Automated Clients Management

Automate clients operations by combining multiple timelink API endpoints. Agents can create client and then list clients in a single workflow.

Example prompt: Call POST /clients to create client, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call timelink 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.

Example prompt: Search Jentic for 'get token details', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/token` | Get token details |
| POST | `/clients` | Create client |
| GET | `/clients` | List clients |
| POST | `/clients/search` | Search clients |
| GET | `/clients/{id}` | Get client |
| PUT | `/clients/{id}` | Update client |
| PATCH | `/clients/{id}` | Partially update client |
| DELETE | `/clients/{id}` | Delete client |

## Key resources

- **Clients** — Operations related to Clients
- **Company** — Operations related to Company
- **Projects** — Operations related to Projects
- **Services** — Operations related to Services
- **Time Entries** — Operations related to Time Entries

## Why Jentic

- **Setup:** Wiring the timelink API by hand means handling its bearer token, working through its client endpoints, and managing retries yourself. Through Jentic you install once, import timelink from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** timelink puts the client id in the URL path (`/clients/{id}`), so a rule can pin your agent to one client: it can read and update that client and nothing else. You choose the operations it may call, so a destructive one like client deletion is not included unless you add it.
- **Credential handling:** Your timelink 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.
- **Discovery method:** Agents search Jentic by intent such as 'search for a client' or 'update a client record', and Jentic returns the matching timelink 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 timelink API use?

The timelink 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 get token details with the timelink API?

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

### What are the rate limits for the timelink 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 token details through Jentic?

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

### How many endpoints does the timelink API have?

The timelink API exposes 39 endpoints covering clients, company, projects operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which timelink operations and credentials the agent may use. Because the client id sits in the URL path (`/clients/{id}`), you can pin the agent to a single client and let it read and update only that record. You also choose the exact operations it may call, so a destructive one like DELETE `/clients/{id}` stays out of reach unless you explicitly add it.