Overview
Everything on the Taskade developer platform uses one credential. Each surface connects to the workspaces that your account already uses.
Get that credential first. Then make your first request and choose between the two API shapes.
┌─ 1. Get a token ────────────────────────────────────────────┐
│ taskade.com/settings/api → tskdp_… (shown once) │
└───────────────────────────┬─────────────────────────────────┘
│
┌─ 2. Send it on every call ▼─────────────────────────────────┐
│ Authorization: Bearer tskdp_… │
└───────────────────────────┬─────────────────────────────────┘
│
┌─ 3. Pick a shape ─────────▼─────────────────────────────────┐
│ REST v1 → /projects/{id}/tasks resource + verb │
│ Action v2 → /createTask one verb per action │
└─────────────────────────────────────────────────────────────┘
Choose an API
| Question | Answer |
|---|---|
| I need full task CRUD — assignees, dates, notes, custom fields | Either. v1 has the longest track record. v2 gained task writes in August 2026 |
| I am wiring this into an LLM as tools | v2 — one verb per endpoint maps directly onto tool definitions |
| I need webhooks registered programmatically | v2 — POST /webhooks |
| I want the surface with a stability guarantee | v1 — v2 is still 2.0.0-beta |
| I am importing or exporting a whole workspace | Either — both expose bundles |
Availability
| Capability | Plan required |
|---|---|
| REST API v1 and Action API v2 | Free and up for most operations, with two exceptions in both versions. Bundle imports check your plan per item type (see the Bundle import row). The webhook operations, subscribeWebhook and signed registration (POST /webhooks), need Pro or above and return 402 below it. Every other endpoint carries no plan gate |
Signed webhook registration (POST /webhooks) |
Pro and up |
| Bundle import | Per item type. Agents, apps, automations, and agent teams each check your plan |
Hosted MCP (taskade.com/mcp) |
Any paid plan. A Free workspace is filtered out of list_spaces |
Workspace MCP (@taskade/mcp-server) |
Free and up, with one exception. Each tool inherits the gate of the endpoint it wraps. The REST API v1 tools carry no gate. Of the five Action API v2 tools, only subscribeWebhook needs Pro or above |
| Personal access tokens | Any account with a verified email, 5 active tokens max |
Tokens carry no scopes. A valid personal access token grants access to everything that the owning account can reach.Treat the token like a password. If you suspect exposure, revoke the token instead of rotating it.