Public API

When viewing a task via the web client you see the total sprint points on the task regardless of how many assignees are assigned. However, when you click sprint points you can see a breakdown of how many points are assigned by assignee. When I retrieve a task via the clickup api I only receive the total points of the task. I would like for this to be returned as an array, broken down by assignee so that I can programmatically retrieve sprint points per assignee.

Ship an official ClickUp CLI as a deterministic alternative to MCP for agent workflows Problem We are building AI-driven workflows where agents run locally or in CI and need a tool surface that is: deterministic and cheap at runtime self-describing (so agents do not guess capabilities) stable across time (versioned contracts) MCP introduces overhead and token cost due to tool discovery and repeated schema/context exchange. We want a CLI-first interface that is always up to date and can be invoked by agents and automation systems. Request Please ship an official ClickUp CLI that wraps core ClickUp APIs and Automation Webhooks, with the following requirements: Help-first, machine-readable contracts clickup --help and clickup <cmd> --help must be complete and structured include input flags, examples, output schemas, and exit codes JSON by default All commands output strict JSON by default (--human optional) Stable schemas with versioning Stable exit codes 0 success 2 needs_input/validation error 3 blocked/permission/auth/rate limit 4 failed/unexpected Authentication OAuth device flow (ideal), plus optional support for personal tokens for power users Clear scoping to a workspace Core commands (v1) tasks get|search|create|update comments create|list lists get|search webhooks create|test (or automation webhook helpers) docs get|search (if feasible) Safety controls --dry-run to show mutations without applying explicit confirmation flag for destructive operations Auto-update / version pinning ability to force update before run (agent-friendly) ability to pin versions for CI reproducibility Why this matters This enables a “ClickUp as coordination layer” architecture where: ClickUp is the UI + state machine external agents/CLIs do deterministic work in codebases updates are written back to ClickUp reliably This is lower cost and higher control than MCP-style tool calling for many teams. Related Automation webhooks already exist and work well; a CLI would complement them as the execution surface.

Hello, I saw that there's the possibility to update/delete a custom field value from ClickUp API, but there's no chance to edit/update the options of a dropdown. That's my use case: I have another platform with its own list of users, that increase on a daily base I have a ClickUp list, with a custom field that holds the user to whom the task is related I wish that the custom field was a dropdown, restricting the access only to the existing users, but cannot mantain it manually whenerever a new user is added on the other platform

When creating or updating tasks via the API using markdown_description, extra vertical spacing (empty line) is added between different block types: heading to text, text to heading, text to bullet list, and bullet list to text. Consecutive bullet points and consecutive text lines render correctly without extra spacing. The same content typed manually in the editor does not produce this extra spacing. Confirmed with both direct REST API calls and the MCP connector, same behavior. It would be useful to either fix this so the API renders the same as the editor, or provide an option/parameter to control paragraph spacing in markdown_description (e.g. a compact_markdown flag or similar).

I want to add fields that I can update with the API, like Email, ratings, etc.

The ability to link docs to tasks using the API to make recuring doc creation easier and faster.

Summary: We are requesting an API endpoint that allows us to retrieve all comments assigned to a specific user across tasks and lists, without the need to make thousands of requests manually. This feature is essential for businesses managing a large number of tasks and team members within ClickUp, where tracking assigned comments is a critical part of performance and task management. Current Challenge: Currently, there is no direct way to retrieve comments assigned to a user. The existing workaround—making thousands of API requests to retrieve all tasks and filter comments—creates performance bottlenecks, is highly inefficient, and is not scalable for businesses managing large numbers of tasks. This approach not only consumes an excessive amount of resources but also introduces significant delays in retrieving the data. We need a solution that allows us to: Efficiently retrieve all comments assigned to a specific user without looping through thousands of tasks. Have immediate access to this data for business-critical operations. Proposed Solution: A new API endpoint that can: Retrieve all comments assigned to a specific user across all tasks and lists within a space or workspace. Allow for filtering by user ID or email to gather the assigned comments. Ensure efficient data retrieval to avoid the need for making excessive requests or running into performance issues. Why This Matters: This feature would eliminate the need for inefficient workarounds and provide a streamlined solution to track user-specific comments. It would save significant time and resources, allowing businesses to focus on performance management and improve task handling. Given that member resources are already available in ClickUp, the lack of an endpoint for assigned comments seems like an oversight, especially for larger teams managing numerous tasks. Impact: This feature would benefit any organization using ClickUp at scale, enabling more efficient tracking of team performance and task management. By adding this endpoint, ClickUp could offer a much more robust and business-friendly API that better supports its users' needs without forcing reliance on third-party tools.

I use ClickUp as my actual timecard, and I would really like to be able to manage it through the API and ClickUp’s MCP server. Right now, the time-tracking support is only partial. The public API has several time-tracking endpoints, but it still does not let me reliably perform all of the same actions that I can perform through the ClickUp interface. Active, in-progress timers are particularly limited. The MCP server exposes an even smaller subset of the available functionality. I would like the API and MCP server to support the complete timecard workflow, including: Viewing all of my time entries for a day or date range, including taskless entries Starting, stopping, and viewing an active timer Editing an active timer without having to stop it and reconstruct the entry Changing the task associated with an active or completed entry Changing the start time, end time, duration, description, tags, and billable status Stopping an active timer at a specified time rather than only at the current moment Creating taskless time entries Editing and deleting completed entries Finding gaps, overlaps, or duplicate entries Summarizing hours for a day or week The goal is to be able to make a request such as: “Show me today’s timecard, move the active timer to the correct task, change its start time to 9:15, add a 30-minute meeting from this morning, and tell me how much time is still missing from an eight-hour day.” At the moment, I can do pieces of this through the API, pieces through MCP, and the rest only through the ClickUp interface. I would like time tracking to be treated as a complete, manageable resource across both the public API and MCP server.

Get the Time Estimates per assignee in the API. When you enable the ability to set the estimate per assignee, the task endpoint is delivering the total estimate only. To be consistent, It should show the estimate per assignee.

The ability to include mentions in comment text or task descriptions