Getting Started

Getting Started

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 │
  └─────────────────────────────────────────────────────────────┘

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 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.

Start here7