Trune API

Name: Trune API
Brand: Trune API
Availability: InStock

✓ Official Vendor SpecProductivityCollaborationbearer14 EndpointsREST

For Agents

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

Use for: I need to retrospective, I want to retrospectives, Search for retrospective, Find all retrospective

Install Jentic One Beta

Connect the Trune API to your agent

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

Create retrospective

List retrospectives

Get retrospective

Update retrospective

GET STARTED

Start building with Trune API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Trune API for, with concrete tasks.

★ 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.

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.

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.

Search Jentic for 'create retrospective', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

14 endpoints — trune retrospective and agile team collaboration api.

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

POST

/retrospectives

Create retrospective

GET

/retrospectives

List retrospectives

GET

/retrospectives/{retroId}

Get retrospective

PUT

/retrospectives/{retroId}

Update retrospective

DELETE

/retrospectives/{retroId}

Delete retrospective

Why Jentic?

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

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Trune API through Jentic.

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.

Trune API

Connect the Trune API to your agent

Capabilities

Start building with Trune API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs