Tookan API

Name: Tookan API
Brand: Tookan API
Availability: InStock

✓ Official Vendor SpecProductivityTask ManagementapiKey11 EndpointsREST

For Agents

Programmatically create task, get task details. Covers 11 operations with apiKey authentication.

Install Jentic One Beta

Connect the Tookan API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Tookan 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://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 Tookan API.

Create Task

Get Task Details

List Tasks

Update Task

GET STARTED

Start building with Tookan API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Tookan API for, with concrete tasks.

★ Productivity Operations

Use the Tookan API to perform productivity operations programmatically. The API provides 11 endpoints covering core functionality including create task, get task details, list tasks.

Call POST /create_task to create task

Automated Tasks Management

Automate tasks operations by combining multiple Tookan API endpoints. Agents can get task details and then list tasks in a single workflow.

Call POST /get_task_details to get task details, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Tookan 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 apiKey tokens manually.

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

Key Endpoints

11 endpoints — tookan is a delivery management and logistics platform.

METHOD

PATH

DESCRIPTION

POST

/create_task

Create Task

POST

/get_task_details

Get Task Details

POST

/get_job_list

List Tasks

POST

/update_task

Update Task

POST

/delete_task

Delete Task

POST

/add_agent

Create Agent

POST

/view_all_agents

List Agents

POST

/edit_agent

Update Agent

POST

/create_task

Create Task

POST

/get_task_details

Get Task Details

POST

/get_job_list

List Tasks

POST

/update_task

Update Task

POST

/delete_task

Delete Task

POST

/add_agent

Create Agent

Why Jentic?

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

Credential isolation

Your Tookan API key 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 task' or 'get the job list', and Jentic returns the matching Tookan operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Tookan API through Jentic.

What authentication does the Tookan API use?

The Tookan API uses an API key passed in the `api_key` 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 task with the Tookan API?

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

What are the rate limits for the Tookan 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 task through Jentic?

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

How many endpoints does the Tookan API have?

The Tookan API exposes 11 endpoints covering tasks, agents, customers operations.

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

Yes. Because you run Jentic One yourself and set its rules, you decide which Tookan operations your agent may call, so you can allow read and create actions like get task details and create task while withholding destructive ones like delete task. Tookan carries the task or agent target in the request body rather than the URL path, so you scope access at the operation level, granting only the endpoints the agent needs. The Tookan API key is stored once by your own instance and injected at execution time, and any operation you have not allowed simply cannot be invoked.

Tookan API

Connect the Tookan API to your agent

Capabilities

Start building with Tookan API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs