Taskade provides a powerful REST API and Model Context Protocol (MCP) interface for developers to build custom integrations, automate workflows, and extend their workspace capabilities programmatically.
📋 In This Article
💡
The Three Pillars of Workspace DNA — The Developer API connects to all three pillars: Memory (Projects & Databases), Intelligence (AI Agents), and Execution (Automations).
REST API Overview
Taskade's REST API lets you programmatically manage your workspace, projects, tasks, and AI agents. The API follows RESTful conventions and returns JSON responses.
Base URL: https://www.taskade.com/api/v1
Key capabilities:
Projects — Create, read, update, and delete projects and their contents
Tasks — Manage tasks, subtasks, due dates, assignments, and custom fields
Agents — Prompt AI agents programmatically and receive structured responses
Workspaces — Manage workspace settings, members, and permissions
Media — Access and manage media files in your workspace
API v2 (Public API v2)
ℹ️
Vibe Coding + Developer API — Build apps with vibe coding, then extend them programmatically with the Taskade API. Combine natural language app building with REST endpoints, webhooks, and MCP connectors for maximum flexibility.
Taskade's Public API v2 (v6.111.0+) provides improved response formats, better error handling, and enhanced schema documentation. Key improvements include:
Consistent response envelope with
data,meta, anderrorsfieldsImproved pagination with cursor-based navigation
Better type definitions and OpenAPI schema
Enhanced rate limit headers
Authentication
Authenticate API requests using your Personal API Token or OAuth 2.0.
Personal API Token
Generate a personal API token from your Settings → API page. Include it in the Authorization header:
Authorization: Bearer YOUR_API_TOKEN
OAuth 2.0
For apps that need to access Taskade on behalf of other users, use OAuth 2.0 authorization flow:
Register your application in Taskade's developer settings
Redirect users to the authorization endpoint
Exchange the authorization code for an access token
Use the access token in API requests
OIDC (OpenID Connect)
Taskade Genesis apps support OIDC authentication for secure, standardized sign-in. This enables:
Secure app access — Users authenticate via Taskade's OIDC provider before accessing your published Genesis app
User identity verification — Get verified user identity claims (email, name, profile)
Standards-compliant — Full OAuth 2.0 / OpenID Connect protocol support
Agent Public API
The Agent Public API (v6.110.0+) lets you prompt any published AI agent programmatically via REST. This is one of Taskade's most powerful developer features — it turns every AI agent into a callable API endpoint.
How It Works
Publish an agent — Set your agent to "Public" in the agent settings
Get the agent ID — Copy the agent's unique identifier from the share dialog
Send prompts via API — POST your prompt to the agent endpoint
Receive structured responses — Get the agent's response as JSON
Use Cases
Chatbots — Power custom chatbots with your trained Taskade agents
Automated workflows — Trigger agent responses from external systems
Data processing — Send documents for analysis and receive structured output
Multi-agent pipelines — Chain multiple agent calls for complex workflows
SaaS integrations — Embed Taskade AI capabilities into your own applications
💡
The Agent Public API respects your agent's training, knowledge sources, and tool permissions. Your agent will respond with the same intelligence and capabilities it has in Taskade's UI.
MCP Connectors (Model Context Protocol)
MCP v2 (Hosted) is Taskade's implementation of the Model Context Protocol — a universal standard for connecting AI agents to external tools and data sources.
What is MCP?
The Model Context Protocol (MCP) is an open protocol that provides a standardized way for AI models to interact with external tools, APIs, and data sources. Taskade's hosted MCP connectors let you:
Connect to any MCP-compatible service with zero setup — fully managed by Taskade
Use stateless MCP servers for lightweight, scalable integrations (v6.117.0+)
Browse 100+ connectors in the Integrations Directory
Build custom MCP servers to expose your own APIs as AI tools
MCP vs Native Integrations
Taskade supports two integration approaches:
Feature | Native Integrations | MCP Connectors |
Setup | One-click OAuth | Zero setup (hosted) or BYO server |
Actions | Pre-built, Taskade-managed | Any MCP-compatible tool |
Scale | 31 built-in pieces | Unlimited — any MCP server |
Best for | Common workflows (Gmail, Slack, Shopify) | Custom tools, niche APIs, proprietary systems |
Building Custom MCP Servers
Developers can build their own MCP servers to expose custom APIs as tools for Taskade agents and automations:
Implement the MCP protocol — Follow the MCP specification to expose your tools
Host your server — Deploy to any infrastructure (cloud, on-premises, edge)
Connect to Taskade — Add your MCP server URL in Taskade's Integrations settings
Use in agents & automations — Your tools become available as agent capabilities and automation actions
Core API Endpoints
Projects
Method | Endpoint | Description |
GET | /projects | List all projects in a workspace |
POST | /projects | Create a new project |
GET | /projects/:id | Get project details |
PUT | /projects/:id | Update a project |
DELETE | /projects/:id | Delete a project |
Tasks
Method | Endpoint | Description |
GET | /projects/:id/tasks | List tasks in a project |
POST | /projects/:id/tasks | Create a task |
PUT | /tasks/:id | Update a task (title, due date, assignees, custom fields) |
DELETE | /tasks/:id | Delete a task |
POST | /tasks/:id/complete | Mark a task as completed |
Agents
Method | Endpoint | Description |
POST | /agents/:id/prompt | Send a prompt to an agent |
GET | /agents/:id | Get agent metadata and capabilities |
GET | /agents/:id/conversations | List agent conversations |
Webhooks
Taskade supports webhooks for real-time event notifications. Configure webhook URLs in your workspace settings to receive notifications when:
Tasks are created, completed, or updated
Projects are modified
Custom field values change
Agent conversations end
Form submissions are received
Webhooks integrate with the Automation Engine — you can also use the Webhook trigger in automation flows to receive data from external systems.
Rate Limits & Best Practices
Respect rate limits — API responses include rate limit headers. Implement exponential backoff on 429 responses
Use pagination — For large result sets, use cursor-based pagination instead of fetching everything at once
Cache when possible — Cache responses for data that doesn't change frequently
Secure your tokens — Never expose API tokens in client-side code. Use server-side requests
🚀 Start Building
🚀
Ready to build? Create your first Genesis app and use the API to extend it with custom integrations.
🌐 Explore the Community
🌎
Browse apps, agent templates, and automation flows built by the Taskade community at taskade.com/community.
Helpful Links