Public API

Firts of all love the official Clickup MCP server. Our SDLC workflow has been trasnformed with it. One issue we seeing is it uses 34K tokens and that's roughly 17% of claude's 200K context window. Any optimisation that can be done ? Screenshot is from Claude code's "/context" command.

Current only time_spent is available. We need to know the billable vs. non-billable time for our invoicing though. The current only way to get this is to do a lookup of all time entries on each task and roll-up the time, which is request-heavy and error-prone. Adding these values (even just eg. billable, since we can derive the other) would be of tremendous help to us

When a task description is created or updated through the API (markdown_content), tables are rendered with default column widths that have nothing to do with the content. Short columns (dates, amounts) waste space, and the table is much wider than it needs to be. There is currently no way to control this: markdown has no syntax for column widths, the API returns and accepts the description only as plain text or markdown, and even in the UI there is no "fit to content" option - only manual dragging of column borders or "fit container" (full width, equal columns). Requests: 1) an "auto-fit columns to content" option for tables (UI), ideally as the default for tables created from markdown; 2) a way to set table column widths through the API, e.g. an optional parameter on task create/update (auto-fit / full width) or support for a width hint in markdown/HTML tables; 3) optionally, access to the rich-text (delta) format of the description via the API, so integrations can read and write tables with their layout. Use case: we generate task descriptions automatically (accounting summaries with an 8-column table of invoices and amounts) and every time someone has to resize the columns by hand.

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

Hello ClickUp Team, I’m writing to request a feature enhancement to the ClickUp Public API regarding comments on images attached to tasks. I’ve searched extensively through the official Public API documentation and related resources, but I couldn’t find any endpoint or reference that allows creating comments directly on images (image annotations / image comments) within a task via the API. Here’s the context of my use case: I’m building an integration between two different ClickUp workspaces: • One workspace belongs to a marketing agency that I’m a client of. In this workspace, they upload creative files (images) and I usually approve or request changes by commenting directly on the images. • The other workspace belongs to my own travel company, where I want to keep the marketing tasks synchronized for internal tracking and visibility. This integration is being built using Make (Integromat) and relies entirely on ClickUp’s Public API. While I can successfully sync tasks, attachments, and regular task comments, I couldn’t find any way to programmatically create or mirror image-specific comments (the comments attached to a specific position on an image). At the moment, this limitation prevents us from fully syncing the approval and feedback flow between the two workspaces, since image comments are a critical part of the creative review process. I’d like to ask if: • This functionality already exists but is undocumented, or • There are plans to expose image comments / image annotations in the Public API (both for reading and creating them). Adding this capability would greatly improve advanced integrations and multi-workspace workflows, especially for teams working with design approvals. Thank you for your time and for the great product. Best regards, Lucas Frederico

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.

I need to be able to use the internal API to extract the history of a task as it is displayed on the web. After some research, I found that this functionality already exists, but it is not exposed via the public API and can be extracted from the internal web API.

It would be extremely helpful if ClickUp API supported retrieving all task activities/history items through its endpoints. It helps tracking impactful changes on the tasks made by users.

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.