Overview
Everything on the Taskade developer platform takes the same credential and talks to the same substrate. This section covers the credential, the two API shapes, and how to choose between them.
┌─ 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 │
└─────────────────────────────────────────────────────────────┘
Which API should I use?
| 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 — the public API is not plan-gated |
| Outbound webhooks | Pro and up |
| MCP (hosted and workspace) | Any paid plan |
| Personal access tokens | Any account with a verified email, 5 active tokens max |
Tokens carry no scopes. A valid personal access token grants full access to everything the owning account can reach — treat it like a password, and revoke rather than rotate when in doubt.