Developer Platform

Use Taskade APIs to integrate your app. You can also build automations or connect AI tools.

Page type: Concept. Read it to learn what this is and when to use it.

Many teams first build visually with Taskade Genesis. They then extend the app with the API.

Before you start

• A Taskade account with a verified email address. Taskade does not create a token for an unverified account.
• curl in a terminal, or any HTTP client.
• Basic Taskade concepts: workspaces, projects, and tasks. If you are new to Taskade, start with Learn Taskade.

Integration surface at a glance

Choose a surface

Get a token

Use a personal access token for scripts, both APIs, the local MCP server, and hosted MCP callers that set their own headers. Interactive clients can connect to hosted MCP with OAuth 2.0.

1. Go to taskade.com/settings/api.
2. Go to Personal access tokens and click Create token.
3. Give the token a descriptive name.
4. Copy the token. Taskade does not show it again.
5. Save the token in your terminal:

export TASKADE_TOKEN="tskdp_your_token_here"

Treat your API token like a password. Never commit it to version control or share it publicly.

Base URLs

Taskade ships two public HTTP APIs. Both APIs use the same token:

Live OpenAPI specs (source of truth) come from the running API:

• REST API v1 - interactive docs · openapi.json
• Action API v2 - interactive docs · openapi.json
• API catalog (RFC 9727) - /.well-known/api-catalog links both specs and the hosted MCP server, so an agent can find them from one URL

The /docs/rest/* and /docs/actions/* catalogs come from committed OpenAPI snapshots.

The Getting Started, Guides, and MCP pages contain hand-written examples and patterns.

For an exact field or status code, use the generated catalog and its source spec.

Make your first call

Each API lists the projects that your account can open. Send the same token to both.

# REST API v1
curl -s https://www.taskade.com/api/v1/me/projects \
  -H "Authorization: Bearer $TASKADE_TOKEN"

# Action API v2: every operation is a POST with a JSON body
curl -s -X POST https://www.taskade.com/api/v2/listMyProjects \
  -H "Authorization: Bearer $TASKADE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

Both calls return ok: true and an items array. Each item carries the project id and name:

{
  "ok": true,
  "items": [
    { "id": "Pj8sK2nV4wQx6ZbE", "name": "API quickstart" }
  ]
}

The v1 item can also carry icon and completed.

Errors

Both APIs return the same JSON error envelope. The HTTP status matches the code. For example, POST /api/v2/webhooks on a Free plan returns 402:

{
  "ok": false,
  "message": "Webhooks require a Pro plan or higher.",
  "code": "PAYMENT_REQUIRED",
  "statusMessage": "Payment Required"
}

Branch on ok and code. Do not parse message.

Some PAYMENT_REQUIRED errors also carry a featureId field. It names the plan entitlement that the request needs. For example, a bundle export on a plan without export returns featureId: "space.bundle.export".

Developer resources

What you can build

• Custom dashboards that pull data from Taskade workspaces and projects
• CI/CD integrations that create tasks or update statuses on deploy
• AI assistants that manage tasks and agents through the MCP Server
• Internal tools that connect Taskade to your company's systems
• Automation bots that react to events and keep projects in sync

Next steps

• Quickstart: create a project and add tasks in about five minutes.
• Authentication: use OAuth 2.0 when your app acts for other Taskade users.
• Taskade API overview: the REST and Action APIs, side by side.
• Webhooks: get an event when data changes, instead of polling.
• Community apps: working examples built with Taskade.