Getting Started

Getting Started

Get one credential, make your first call, and then pick the API that fits your integration. The pages in this category take you through each step.

Page type: Concept. Use it to pick the page that fits your task.

Overview

The REST API, the Action API, and both Taskade MCP servers accept a personal access token or an OAuth 2.0 access token. Each of these surfaces connects to the workspaces that your account already uses. Public agent embeds need no credential. They use a public agent ID or URL.

Note: New here? Follow the Quickstart first. It takes you from a new personal access token to a project with tasks in about five minutes.

The path has three steps:

  ┌─ 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

Find your question in the table to pick an API version.

Question Answer
I need full task CRUD: assignees, dates, notes, custom fields v1. Only v1 has a call that reads one task, or its assignees, date, note, or field value. v2 writes all of them with named actions
I will expose this as LLM tools v2. One verb for each endpoint maps directly onto tool definitions
I need webhooks registered programmatically v2, with 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

Each surface checks the access of the token owner. Some surfaces also need a plan.

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) Pro and above. Returns a typed access error when the current account cannot register it
Bundle export Pro and above. Other plans get a 402 with featureId: "space.bundle.export"
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
Plan details See pricing

Warning: Treat a personal access token like a password. It carries no workspace scope, so it grants access to everything that its owner can reach. If you suspect exposure, revoke the token and create a new one.

Next steps

  • Quickstart: go from a new token to a project with tasks in about five minutes.
  • Taskade API overview: every endpoint group in the REST and Action APIs, with examples.
  • Authentication: personal access tokens and OAuth 2.0 with PKCE.
  • Webhooks: get an event at your endpoint when data changes.
  • Which MCP?: pick the MCP connection path for your AI tool.

Start here8