July 21, 2026

A signed Webhook Registration API over REST, and eleven new create-and-orchestrate tools on the hosted Taskade MCP.

Developer highlights. This section tracks API, MCP, SDK, automation, and Taskade Genesis platform changes for developers. For the full product changelog see taskade.com/changelog; for release newsletters see taskade.com/blog/updates.

What's New:

Webhook Registration API: Signed Outbound Webhooks over REST

The Action API v2 gains a REST-style Webhook Registration API with signed deliveries. POST /api/v2/webhooks registers a target URL for one or more events and returns an HMAC signing secret exactly once — every delivery then carries an X-Taskade-Signature header (sha256= + HMAC-SHA256 hex digest of the raw body) that your endpoint can verify. Manage endpoints with GET /webhooks and GET/DELETE /webhooks/{id} (the id is the URL-encoded target URL), and scope registrations to specific workspaces with spaceIds (empty = all). Six event types are supported at launch — see the event reference. Requires Pro or above; the legacy subscribeWebhook / unsubscribeWebhook operations are deprecated but continue to work. See Webhooks.

---

Hosted Taskade MCP: Create & Orchestrate Tools

The hosted Taskade MCP server at taskade.com/mcp now mirrors the core of the Action API v2 — connected AI clients can create and orchestrate, not just browse:

Area	New tools
Projects & tasks	create_project, list_tasks
Agents	create_agent, get_agent, update_agent, delete_agent, prompt_agent
Agent knowledge	add_knowledge_project, remove_knowledge_project
Conversations	list_conversations, get_conversation

They join the existing list_spaces, list_projects, list_agents, and MCP-native tools (inspect_space, read_project, list_automations, write_file), and a new taskade://getting-started resource walks AI clients through the workflow. On the API side, POST /getConversation now accepts includeTranscript: true to return a Markdown transcript of an agent conversation.