Getting Started

Developer Platform

5 min readStart here
Getting Started

You want to integrate Taskade into your app, automate your workflows, or connect your AI tools. This page gets you started fast. Many teams build their app visually with Taskade Genesis first, then extend it 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 data to Claude Desktop, Cursor, or other MCP clients Workspace MCP + Advanced
Call another MCP server's tools from a flow 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

You need a Personal Access Token to authenticate with every Taskade developer tool — the REST API, MCP Server, and SDK all use it.

  1. Go to taskade.com/settings/api.
  2. Click Create new token and give it a descriptive name.
  3. Copy the token and store it somewhere safe. You will not be able to see it again.


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

Developer Resources

Resource Description
REST API v1 Reference The complete, stable RESTful API — full task CRUD, per-endpoint docs
Action API v2 Reference The newer action-based (RPC) API — agent prompting, bundles, lifecycle
Authentication Guide Personal access tokens and OAuth 2.0 (PKCE) flows
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 Orchestrate your workspace from your IDE — create projects, manage & prompt agents, and edit your Genesis app's source via the remote https://www.taskade.com/mcp server
MCP Client connector Outbound MCP: point an automation at any remote MCP server and call its tools as flow steps. Agents delegate to the automation — they don't 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; call out to 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 — not yet on public npm; use the REST API meanwhile


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}) Prompting agents, agent lifecycle, bundles, signed webhooks, task CRUD


Live OpenAPI specs (source of truth) — auto-generated from the running API, always current:

The reference pages in this guide are hand-written companions (examples, patterns, best practices). When in doubt about an exact field or status code, the live spec wins.

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 come back as typed errors, not bare 500s:

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

The HTTP status matches the code (e.g. 401 UNAUTHORIZED, 402 PAYMENT_REQUIRED, 403 FORBIDDEN, 404 NOT_FOUND, 429 TOO_MANY_REQUESTS). Branch on ok and code rather than parsing 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