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. Then choose between the two API shapes.


New here? Follow the Quickstart first. It walks you from a fresh personal access token to a project with tasks, in about five minutes. This page maps every surface for after that first call.

  ┌─ 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 maps each write to a named action
I will expose this as LLM 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 will import or export a whole workspace Either - both expose bundles

Access and availability

Capability Access behavior
REST API v1 and Action API v2 Each operation checks the token owner's permissions and the target workspace
Signed webhook registration (POST /webhooks) Returns a typed access error when the current account cannot register it
Bundle import Validates each resource against the target workspace's current access and limits
Hosted MCP (taskade.com/mcp) Lists and operates on workspaces with MCP access. Available on every paid plan (Starter and above)
Workspace MCP (@taskade/mcp-server) Inherits the access rules of each API operation
MCP Client connector Runs inside a Taskade automation. It connects to an external HTTPS MCP server. Available on every plan, including Free
Public agent embeds Require a public agent ID or public agent URL
Personal Access Tokens Grant the token owner's existing access


Personal Access Tokens carry no workspace scope. A valid token grants access to everything that its owner can reach.

Treat the token like a password. If you suspect exposure, revoke it. Then create a replacement.

See pricing for current plan details.

Start here8