Getting Started

Developer Platform

6 min readStart here
Getting Started

Use Taskade APIs to integrate your app, automate workflows, or connect AI tools.

Many teams first build visually with Taskade Genesis. They then extend the app with the API.

Integration Surface at a Glance

I Want To...

I want to... Use
Write tasks, manage assignees/dates/fields (full CRUD) Either — REST API v1 or Action API v2
Prompt agents, register signed webhooks Action API v2
Manage agents, export/import bundles Either version
Hit endpoints from any language REST API v1 + Action API v2
Expose Taskade projects, tasks, and agents to Claude Desktop, Cursor, or other MCP clients Hosted Taskade MCP or Workspace MCP
Call another MCP server's tools from an automation MCP Client connector
Edit Taskade Genesis app source code from your IDE Hosted MCP (Genesis App)
Receive real-time events in your app Webhooks
Understand long-term memory Long-Term Memory
Build agents that run without prompting Autonomous Agents
Automate workflows without code Automations Engine
Browse community apps and templates taskade.com/apps

Get Your API Key

Use a Personal Access Token for scripts, both APIs, the local MCP server, and header-controlled hosted MCP callers.

Interactive clients can connect to hosted MCP with OAuth 2.0.

  1. Go to taskade.com/settings/api.
  2. Click Create token.
  3. Give the token a descriptive name.
  4. Copy the token. Taskade does not show it again.
  5. Store the token in a secret manager or environment variable.


Treat your API token like a password. Never commit it to version control or share it publicly.

Developer Resources

Resource Description
REST Endpoint Catalog Generated from the committed v1 OpenAPI spec — exact methods, parameters, and response schemas
Actions Endpoint Catalog Generated from the committed v2 OpenAPI spec — exact operation bodies and response schemas
REST API Guide Hand-written REST concepts, examples, and usage patterns
Action API Guide Hand-written action/RPC concepts, examples, and usage patterns
Authentication Guide Personal access tokens and OAuth 2.0 (PKCE), including both hosted MCP options
Workspace MCP Run @taskade/mcp-server to connect Claude Desktop, Cursor, and Claude Code (source)
Workspace MCP — Advanced Multi-client setup, troubleshooting, security
Hosted Taskade MCP Use OAuth or a Personal Access Token with the remote https://www.taskade.com/mcp server to create projects, edit tasks, manage and prompt agents, and edit Taskade Genesis app source
MCP Client connector Outbound MCP: point an automation at a remote MCP server. Agents delegate to the automation and do not call MCP servers directly (which MCP?)
Integration Kit (GitHub) Open-source Zapier and n8n actions & triggers built on the public API — contribute or self-host
Webhooks Trigger automations from external events and call any API
Bundles & App Kits Import/export full Genesis apps as portable .tsk bundles
Long-Term Memory Memory-as-Projects architecture — editable, queryable, API-addressable
Autonomous Agents Automations, orchestration, cross-agent invocation patterns
TypeScript SDK (Preview) Generated client for v2. It is not yet on public npm, so use the REST API


New to Taskade? Start with the Quick Start Guide to understand workspaces, projects, and tasks before diving into the API.

Base URLs

Taskade ships two public HTTP APIs, both authenticated with the same token:

API Base URL Style Use it for
REST API v1 https://www.taskade.com/api/v1 RESTful (GET/POST/PUT/DELETE) Full task CRUD, assignees, dates, notes, fields
Action API v2 https://www.taskade.com/api/v2 Action / RPC (POST /{operation}), with REST-style exceptions for media, bundle downloads, and webhook registration Prompting agents, agent lifecycle, bundles, signed webhooks, task CRUD


Live OpenAPI specs (source of truth) come from the running API:

The /docs/rest/* and /docs/actions/* catalogs come from committed OpenAPI snapshots.

The Getting Started, Guides, and MCP pages contain hand-written examples and patterns.

For an exact field or status code, use the generated catalog and its source spec.

Include your token in the Authorization header:

Bash
# v1 (RESTful)
curl -H "Authorization: Bearer your_api_key_placeholder" \
     https://www.taskade.com/api/v1/me/projects

# v2 (action-based — every call is a POST)
curl -X POST https://www.taskade.com/api/v2/listMyProjects \
     -H "Authorization: Bearer your_api_key_placeholder" \
     -H "Content-Type: application/json" -d '{}'

Errors

Both APIs return a consistent JSON error envelope. Expected failures return typed errors instead of bare 500 responses:

Json
{
  "ok": false,
  "code": "PAYMENT_REQUIRED",
  "message": "Webhooks require a Pro plan or higher.",
  "statusMessage": "Payment Required"
}

The HTTP status matches the code. Codes are upper-case identifiers such as UNAUTHORIZED (401), PAYMENT_REQUIRED (402), NOT_FOUND (404), and TOO_MANY_REQUESTS (429).

Branch on ok and code. Do not parse message.

What You Can Build

  • Custom dashboards that pull data from Taskade workspaces and projects
  • CI/CD integrations that create tasks or update statuses on deploy
  • AI assistants that manage tasks and agents through the MCP Server
  • Internal tools that connect Taskade to your company's systems
  • Automation bots that react to events and keep projects in sync


Need help? Browse community apps for working examples, or reach out to support at taskade.com/contact.

NextDeveloper Overview