Keltehue

Name: Keltehue API
Brand: Keltehue
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityTask Managementbearer6 EndpointsREST

For Agents

Authenticate against Keltehue, then read and create tasks, list notes, and fetch the current user's profile through six bearer-authenticated REST endpoints.

Install Jentic One Beta

Connect the Keltehue to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Keltehue, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Keltehue API.

Exchange username and password at /Auth/Login for a bearer token

List the tasks visible to the authenticated Keltehue user

Create a new task in Keltehue with the POST /api/task endpoint

Fetch a single task by ID for downstream display or processing

GET STARTED

Start building with Keltehue API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Keltehue API for, with concrete tasks.

★ Task Synchronisation with External Tools

Keep tasks consistent between Keltehue and a primary task tracker such as Asana or ClickUp by listing Keltehue tasks on a schedule and writing matching items into the external tool. The /api/task endpoints support both list and create flows, and /api/task/{id} provides a single-record read for delta checks. A daily cron-driven sync ships in well under a day.

GET /api/task to list Keltehue tasks, then POST each new task into the external task tracker using its task-create endpoint

Note Aggregation Dashboard

Aggregate notes from Keltehue into a knowledge dashboard or search index by listing notes through GET /api/note. Notes can then be indexed alongside content from other sources to produce a unified search experience. The bearer token issued at /Auth/Login is valid for the duration of the session and is reused across both note and task reads.

POST /Auth/Login to obtain a bearer, then GET /api/note and write the response into a search index

AI Agent Task Capture

An AI agent that captures action items during meetings calls Keltehue's task-create endpoint via Jentic to push each action item into the user's Keltehue task list. The agent searches Jentic by intent ('create a task in keltehue'), loads the schema, and submits the task title and metadata in a single execute call. The bearer token is held in Jentic's vault and refreshed on the agent's behalf.

Use Jentic to execute POST /api/task with a title extracted from the meeting transcript and the user's bearer token injected automatically

Key Endpoints

6 endpoints — keltehue is an organisational information system that keeps teams informed from operational tasks up through strategic notes.

METHOD

PATH

DESCRIPTION

POST

/Auth/Login

Exchange credentials for a bearer token

GET

/api/me

Read the current user's profile

GET

/api/task

List tasks visible to the user

POST

/api/task

Create a new task

GET

/api/task/{id}

Read a single task by ID

GET

/api/note

List notes the user can access

POST

/Auth/Login

Exchange credentials for a bearer token

GET

/api/me

Read the current user's profile

GET

/api/task

List tasks visible to the user

POST

/api/task

Create a new task

GET

/api/task/{id}

Read a single task by ID

GET

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Keltehue username and password are stored encrypted in the Jentic vault. Jentic exchanges them at /Auth/Login on the agent's behalf and reuses the bearer token across calls, so neither the password nor the bearer ever appears in the agent's context.

Intent-based discovery

Agents search by intent (e.g. 'create a task in keltehue') and Jentic returns the matching Keltehue operation with its input schema attached.

Time to first call

Direct Keltehue integration: half a day for login, token storage, and the small handful of endpoints. Through Jentic: under 30 minutes — search, load, execute.

FAQs

Specific to using Keltehue API through Jentic.

What authentication does the Keltehue API use?

POST username and password to /Auth/Login to exchange credentials for a bearer token, then send the token in the Authorization header on every subsequent request. Through Jentic, the username and password are held in the encrypted vault and the bearer token is minted and refreshed for the agent automatically.

Can I create a task with the Keltehue API?

Yes. POST /api/task with the task title and any required metadata creates a new task in the authenticated user's Keltehue account. After creation, GET /api/task/{id} returns the full record so you can confirm the create succeeded.

What are the rate limits for the Keltehue API?

The OpenAPI spec does not declare numeric rate limits. With only six endpoints the surface is small, so most callers stay well within whatever limits Keltehue applies at the platform level. If you receive HTTP 429, back off and retry.

How do I list my Keltehue tasks through Jentic?

Search Jentic for 'list tasks in keltehue' to find GET /api/task, load its schema, and execute it. Jentic injects the bearer token automatically. The standard flow is pip install jentic, then client.search, client.load, and client.execute.

Does the Keltehue API expose notes?

Yes, but only as a list read. GET /api/note returns the notes the authenticated user can see; the public spec does not expose a note-create or note-update endpoint, so writes must happen through the Keltehue UI.

Keltehue

Connect the Keltehue to your agent

Capabilities

Start building with Keltehue API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs