Developer Platform
Everything you need to build on Taskade — REST API, MCP Server, SDK, and more.
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...
Write tasks, manage assignees/dates/fields (full CRUD)
Prompt agents, manage agents, export/import bundles
Hit endpoints from any language
Expose Taskade data to Claude Desktop, Cursor, or other MCP clients
Give a Taskade agent third-party capabilities
Edit Taskade Genesis app source code from your IDE
Receive real-time events in your app
Understand long-term memory
Build agents that run without prompting
Automate workflows without code
Browse community apps and templates
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.
Go to taskade.com/settings/api.
Click Create new token and give it a descriptive name.
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
The complete, stable RESTful API — full task CRUD, per-endpoint docs
The newer action-based (RPC) API — agent prompting, bundles, lifecycle
Personal access tokens and OAuth 2.0 (PKCE) flows
Run @taskade/mcp-server to connect Claude Desktop, Cursor, and Claude Code (source)
Multi-client setup, troubleshooting, security
Edit your Genesis app's source from your IDE via the remote https://www.taskade.com/mcp server
Give Taskade agents 31+ third-party tools (outbound MCP)
Open-source Zapier and n8n actions & triggers built on the public API — contribute or self-host
Trigger automations from external events; call out to any API
Import/export full Genesis apps as portable .tsk bundles
Memory-as-Projects architecture — editable, queryable, API-addressable
Automations, orchestration, cross-agent invocation patterns
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:
https://www.taskade.com/api/v1
RESTful (GET/POST/PUT/DELETE)
Full task CRUD, assignees, dates, notes, fields
https://www.taskade.com/api/v2
Action / RPC (POST /{operation})
Prompting agents, agent lifecycle, bundles
Live OpenAPI specs (source of truth) — auto-generated from the running API, always current:
REST API v1 — interactive docs · openapi.json
Action API v2 — interactive docs · openapi.json
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:
Errors
Both APIs return a consistent JSON error envelope — expected failures come back as typed errors, not bare 500s:
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? Join the Taskade community or reach out to support at taskade.com/contact.
Last updated
Was this helpful?