For Agents
Create and list projects and tasks in CatchUp so external systems and AI agents can record work items in one place.
Get started with CatchUp API in minutes using your preferred integration method.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"create a CatchUp task"
# → Jentic returns the GET /events tool with parameter schema, agent executes.What an agent can do with CatchUp API API.
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
GET STARTED
Use for: I need to create a new project in CatchUp, List all my CatchUp projects, Create a CatchUp task for the design review, Find all CatchUp tasks for a specific project
Not supported: Does not handle task updates, deletions, comments, or time tracking — use for listing and creating CatchUp projects and tasks only.
Jentic publishes the only available OpenAPI document for CatchUp API, keeping it validated and agent-ready.
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.
Patterns agents use CatchUp API API for, with concrete tasks.
★ 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.
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.
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.
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.
Search Jentic for 'create a CatchUp task', load POST /tasks, and execute it with the task title and project_id chosen by the agent.
4 endpoints — jentic publishes the only available openapi specification for catchup api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/projects
List all projects
/projects
Create a project
/tasks
List tasks
/tasks
Create a task
/projects
List all projects
/projects
Create a project
/tasks
List tasks
/tasks
Create a task
Three things that make agents converge on Jentic-routed access.
Credential isolation
CatchUp API keys are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access at execution time and the raw key never enters prompts, logs, or response payloads.
Intent-based discovery
Agents search by intent (e.g., 'create a task' or 'list projects') and Jentic returns the matching CatchUp operation along with its input schema, so the agent calls the correct endpoint without browsing docs.
Time to first call
Direct CatchUp integration including key handling and project-scoping logic: about half a day. Through Jentic: under 30 minutes — search, load, execute.
Alternatives and complements available in the Jentic catalogue.
Asana API
Asana is a richer project management alternative with full task lifecycle endpoints.
Choose Asana when you need to update, comment on, or close tasks via API; CatchUp's current spec only supports list and create.
Linear API
Linear is an engineering-focused alternative with a GraphQL surface.
Pick Linear for software-engineering issue tracking with cycles and projects; pick CatchUp for a lighter generic task list.
ClickUp API
ClickUp is a feature-broad alternative covering tasks, docs, goals, and time tracking.
Use ClickUp when teams want one tool for tasks, docs, and OKRs; use CatchUp when scope is just projects and tasks.
Specific to using CatchUp API API through Jentic.
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 at https://app.jentic.com/sign-up.
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 the MAXsystem vault 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.