Checkvist API

Name: Checkvist API API
Brand: Checkvist API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityTask ManagementapiKey18 EndpointsREST

For Agents

Create and update Checkvist checklists, tasks, and comments so an agent can manage hierarchical to-do lists, import tasks in bulk, and pull task threads.

Connect the Checkvist API to your agent

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

Install Jentic One Beta (Self-Hosted)

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

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 Checkvist API API.

Create checklists and update their settings or visibility

Add, update, and delete tasks at any depth of a checklist

Bulk-import tasks into a checklist from text or another source

Read, post, and edit comments threaded under tasks

GET STARTED

Start building with Checkvist API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Checkvist API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Checkvist API, keeping it validated and agent-ready. Checkvist is a hierarchical task and outline manager popular with developers and writers who prefer keyboard-driven nested lists over rigid kanban boards. The API exposes 18 endpoints covering authentication, checklists, tasks (with arbitrarily deep nesting), comments, and a bulk import operation. It is suited to teams scripting checklist generation, syncing tasks to other systems, or building custom front-ends on top of Checkvist.

Use Cases

Patterns agents use Checkvist API API for, with concrete tasks.

★ Bulk Task Import from Notes

Convert structured meeting notes or a roadmap document into a Checkvist outline in one call. The script POSTs the parsed tasks to /checklists/{id}/import.json with the tab-indented body Checkvist expects, preserving hierarchy. Useful for teams that brainstorm in a doc and want the action items mirrored in their tracker without retyping.

POST a tab-indented task list to /checklists/{id}/import.json for checklist_id 12345 and confirm the imported task ids.

Cross-Tool Task Sync

Mirror Checkvist tasks into a calendar, time tracker, or daily standup tool. A scheduled job pulls /checklists/{id}/tasks.json, transforms tasks with due dates into events or entries, and posts them downstream. Useful for solo operators living inside Checkvist who want their tasks appearing in shared team systems.

Pull /checklists/{id}/tasks.json for checklist_id 12345 and return the count of tasks due in the next 7 days.

Threaded Task Discussions

Treat Checkvist tasks like lightweight tickets by reading and posting comments programmatically. /checklists/{id}/tasks/{task_id}/comments.json supports listing existing comments and posting new ones, which a chat or email integration can use to surface task discussions in another tool.

Post a comment to /checklists/{id}/tasks/{task_id}/comments.json for task_id 7777 with content 'Blocked on design review'.

AI Agent for Outline Management

An autonomous agent receives ad hoc instructions ('add three subtasks under task 42 about deployment, monitoring, and rollback') and translates them into Checkvist API calls through Jentic. The X-Client-Token never enters the agent's prompt — Jentic injects it from the MAXsystem vault.

Through Jentic, search 'create a task in checkvist', load the schema for /checklists/{id}/tasks.json, and execute with checklist_id 12345 and content 'Write release notes'.

Key Endpoints

18 endpoints — jentic publishes the only available openapi specification for checkvist api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/auth/login.json

Obtain an authentication token

GET

/checklists.json

List user checklists

POST

/checklists.json

Create a checklist

GET

/checklists/{id}/tasks.json

List tasks in a checklist

POST

/checklists/{id}/tasks.json

Create a task

POST

/checklists/{id}/import.json

Bulk import tasks into a checklist

POST

/checklists/{id}/tasks/{task_id}/comments.json

Why though Jentic?

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

Credential isolation

Checkvist credentials and X-Client-Token values are stored encrypted in the Jentic MAXsystem vault. The agent never holds either — Jentic logs in via /auth/login.json, refreshes tokens, and injects the header at execution time.

Intent-based discovery

Agents search Jentic by intent (e.g. 'create a task in checkvist' or 'import tasks') and Jentic returns the matching Checkvist operation with its input schema, so the agent picks among 18 endpoints without reading docs.

Time to first call

Direct Checkvist integration: about a day for token exchange, refresh, and the indented import format. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Chatwork API

Team chat with its own task feature; useful for posting Checkvist updates into a chat room

Choose Chatwork when communicating progress; Checkvist is the hierarchical task source

Alternative

Checkmob API

Field service work order management — different domain (mobile field jobs vs personal/team outlines)

Choose Checkmob for field technician work orders, not personal task outlines

Complementary

Checkly Public API

Synthetic monitoring you can use to verify Checkvist endpoints stay healthy

Choose Checkly to monitor uptime of the Checkvist API for an integration

FAQs

Specific to using Checkvist API API through Jentic.

Why is there no official OpenAPI spec for Checkvist API?

Checkvist publishes API documentation but not a maintained OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Checkvist API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Checkvist API use?

Checkvist uses an API token passed in the X-Client-Token header. You obtain a token by POSTing credentials to /auth/login.json and can refresh it via /auth/refresh_token.json. Through Jentic, both credentials and the resulting token live in the MAXsystem vault and are injected at execution time.

Can I create nested tasks with the Checkvist API?

Yes. POST /checklists/{id}/tasks.json accepts a parent_id parameter so you can place a task under any existing task to build a hierarchy. The same endpoint returns the new task id, which you can then nest further by referencing it as parent_id on subsequent calls.

How do I bulk import tasks into Checkvist via the API?

Use POST /checklists/{id}/import.json with a tab-indented text body that represents the desired hierarchy (one task per line, indentation for nesting). The endpoint creates all tasks in a single call and returns the imported task ids.

What are the rate limits for the Checkvist API?

The OpenAPI specification does not declare formal rate limits. Plan for retry-with-backoff on 429 responses and refresh tokens proactively via /auth/refresh_token.json before they expire to avoid auth churn in long-running scripts.

How do I create a Checkvist task through Jentic?

Install the SDK with `pip install jentic`, then call Jentic.search('create a task in checkvist'), load the schema for /checklists/{id}/tasks.json, and execute with the checklist id and task content. Jentic handles login, token refresh, and X-Client-Token injection.