canonical: https://jentic.com/apis/catchup.cloud/catchup

# CatchUp API

Jentic publishes the only available OpenAPI specification for CatchUp API, keeping it validated and agent-ready. CatchUp is a project and task management platform aimed at small teams that want a lightweight surface for tracking work. The API exposes the two core resources - projects and tasks - with list and create operations on each, suitable for piping issues from external tools, generating recurring task batches, or spinning up a project from a template. It is intended for embedding CatchUp into onboarding scripts, internal tools, and AI agent workflows that need to record work items somewhere central.

## For AI agents

Create and list projects and tasks in CatchUp so external systems and AI agents can record work items in one place.

## Scope

Does not handle task updates, deletions, comments, or time tracking - use for listing and creating CatchUp projects and tasks only.

## Capabilities

- List all projects in a CatchUp workspace
- Create a new project in CatchUp with a name and metadata
- List tasks across the workspace, optionally filtered by project
- Create a new task in CatchUp linked to a project

## Use cases

### Onboarding-driven project setup

When a new client signs up, an automation can POST /projects with a templated name, then POST /tasks repeatedly with the standard checklist of onboarding items pre-assigned. This removes the manual spinning-up step and ensures every engagement starts with the same scaffolding.

Example prompt: POST /projects with name='Acme Onboarding', then POST /tasks four times with that project_id and the standard onboarding task names.

### Capture follow-ups from meetings

A meeting-bot or AI assistant can convert action items from a recap into CatchUp tasks via POST /tasks, attaching them to the right project. The user later sees the tasks in CatchUp without manually transcribing the recap.

Example prompt: For each action item in the recap, POST /tasks with title, due_date, and the active project_id.

### Cross-tool task aggregation

Teams using CatchUp as the canonical task list can pipe issues from GitHub or Linear into it via POST /tasks, keeping a single pane of glass. The list endpoints make it easy to detect duplicates before creating new entries.

Example prompt: GET /tasks for the project, then POST /tasks for each new GitHub issue that does not already match by title.

### AI agent task tracking via Jentic

An AI productivity agent can record its own work plan or follow-ups as tasks in CatchUp through Jentic, so the human user has a transparent record of what the agent committed to. Jentic stores the API key in the vault and never exposes it in the agent's prompt.

Example prompt: Search Jentic for 'create a CatchUp task', load POST /tasks, and execute it with the task title and project_id chosen by the agent.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/projects` | List all projects |
| POST | `/projects` | Create a project |
| GET | `/tasks` | List tasks |
| POST | `/tasks` | Create a task |

## Key resources

- **Projects** — List and create projects that group related tasks.
- **Tasks** — List and create individual tasks attached to projects.

## Why Jentic

- **Setup:** Wiring CatchUp by hand means learning its API key header and building the request bodies for creating projects and tasks yourself. Through Jentic you install once, import CatchUp from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** CatchUp identifies the project or task in the request body rather than the URL path, so scope your agent to the operations it needs, such as listing projects or creating a task, and leave the rest out. Every operation you credit it with is one you have added to the allowed set.
- **Credential handling:** Your CatchUp 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.
- **Discovery method:** Agents search Jentic by intent such as 'create a task' or 'list projects', and Jentic returns the matching CatchUp operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Asana API** — Asana is a richer project management alternative with full task lifecycle endpoints.
- **Linear API** — Linear is an engineering-focused alternative with a GraphQL surface.
- **ClickUp API** — ClickUp is a feature-broad alternative covering tasks, docs, goals, and time tracking.

## FAQ

### Why is there no official OpenAPI spec for CatchUp API?

CatchUp publishes documentation but no machine-readable OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call CatchUp API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the CatchUp API use?

The CatchUp API uses an API key passed in the Authorization header. Generate the key inside CatchUp and include it on every request. Through Jentic, the key is stored encrypted in your Jentic One instance and injected at execution time, so it never enters the agent's prompt.

### Can I update or delete CatchUp tasks via the API?

No. The current OpenAPI spec exposes only list and create operations on /projects and /tasks. Editing or removing existing records is done in the CatchUp web UI.

### What are the rate limits for the CatchUp API?

CatchUp does not document explicit rate limits in this OpenAPI spec. Avoid tight polling against /tasks; refresh on a fixed interval instead, and batch task creation by issuing parallel requests with reasonable concurrency.

### How do I create a CatchUp task through Jentic?

Run pip install jentic, search Jentic with the query 'create a CatchUp task', load the POST /tasks schema, and execute it with the task title and the chosen project_id from GET /projects. Jentic injects the API key from the vault automatically.

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

Yes. Because you run Jentic One yourself, your own rules decide which CatchUp operations and credentials the agent can use, so you can grant only the ones it needs. The API has just four operations: listing projects, creating a project, listing tasks, and creating a task. You might allow an agent to run GET /projects and POST /tasks while withholding POST /projects, since every operation you credit it with is one you have added to the allowed set.