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

# Trune API

Trune retrospective and agile team collaboration API. Manage retrospectives, action items, and team feedback. The API exposes 14 endpoints secured with bearer authentication.

## For AI agents

Programmatically create retrospective, list retrospectives. Covers 14 operations with bearer authentication.

## Scope

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

## Capabilities

- Create retrospective
- List retrospectives
- Get retrospective
- Update retrospective
- Delete retrospective
- Add feedback to retrospective

## Use cases

### Productivity Operations

Use the Trune API to perform productivity operations programmatically. The API provides 14 endpoints covering core functionality including create retrospective, list retrospectives, get retrospective.

Example prompt: Call POST /retrospectives to create retrospective

### Automated Retrospectives Management

Automate retrospectives operations by combining multiple Trune API endpoints. Agents can list retrospectives and then get retrospective in a single workflow.

Example prompt: Call GET /retrospectives to list retrospectives, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Trune 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 'create retrospective', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/retrospectives` | Create retrospective |
| GET | `/retrospectives` | List retrospectives |
| GET | `/retrospectives/{retroId}` | Get retrospective |
| PUT | `/retrospectives/{retroId}` | Update retrospective |
| DELETE | `/retrospectives/{retroId}` | Delete retrospective |
| POST | `/retrospectives/{retroId}/feedback` | Add feedback to retrospective |
| POST | `/action-items` | Create action item |
| GET | `/action-items` | List action items |

## Key resources

- **Retrospectives** — Retrospective management
- **Action Items** — Action item tracking
- **Teams** — Team management

## Why Jentic

- **Setup:** Wiring Trune API by hand means learning its bearer auth, tracking retrospective ids across calls, and handling errors and retries yourself. Through Jentic you install once, import Trune API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Trune API puts the retrospective id in the URL path (`/retrospectives/{retroId}/...`), so a rule can pin your agent to one retrospective: it can read it and add feedback and nothing else. You choose the operations it may call, so deleting a retrospective is not included unless you add it.
- **Credential handling:** Your Trune API 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 'create a retrospective' or 'add feedback to a retro', and Jentic returns the matching Trune API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Asana** — Alternative productivity API
- **Monday** — Alternative productivity API
- **Clickup** — Complementary productivity API

## FAQ

### What authentication does the Trune API use?

The Trune 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 create retrospective with the Trune API?

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

### What are the rate limits for the Trune 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 create retrospective through Jentic?

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

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

The Trune API exposes 14 endpoints covering retrospectives, action items, teams operations.

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

Yes. Because Jentic One is self-hosted, your own rules decide which Trune API operations and credentials the agent may use. Since the Trune API puts the retrospective id in the URL path, such as `/retrospectives/{retroId}/feedback`, you can pin the agent to a single retrospective so it reads that retro and adds feedback and nothing else. You choose the operations it can call, so deleting a retrospective or creating action items stays off limits unless you explicitly allow it.