Public API

I use ClickUp's Personal List to keep my personal tasks separate from my work — which is the very reason the feature exists. But I can't reach it from Claude through ClickUp's MCP Server: when I ask Claude to look at my Personal List, it can't see it at all. Request: make Personal List accessible via MCP, so AI assistants can both read Personal List tasks (list, search, surface alongside other work) and create/update them from the assistant. Both read and write matter — capturing a task into Personal List from Claude is just as valuable as reading what's already there. Right now Personal List is a blind spot for any connected AI assistant. It's the one part of my workspace I deliberately keep separate, and that separation means I can't bring it into an AI workflow at all without breaking it. (Related API-layer request: "Access Personal List through the API" — the two reinforce each other.)

I use ClickUp's Notepad extensively — hundreds of notes captured over time. It's become a core part of how I work, but I've hit a hard wall: Notepad isn't accessible through the Public API at all, which also means it's invisible to the ClickUp MCP Server and any AI assistant (e.g. Claude) connected through it. This is totally limiting. I can't programmatically read, search, or restructure my own notes. Right now, migrating notes into Docs or surfacing note content alongside tasks requires fully manual copy-paste, one note at a time — across hundreds of notes. The data is mine and it's already in ClickUp, but I have no way to reach it programmatically. Request: add read/write API endpoints for Notepad notes (list notes, get note content, create note, update note, delete note), and surface them as MCP tools. Since the MCP Server only exposes what the Public API supports, this has to start at the API layer. Even read-only Notepad endpoints would be a meaningful first step.

Using the API I would like to get the Tasks from the Personal Priority List. Also when using other task-related API-calls (ex. GetFilteredTeamTasks) I would like to get the information, whether a task is on someones Personal Priority List.

We need API endpoints to create, update, and delete task workflow statuses at the List, Folder and Space level, similar to how we can already manage other List/Folder/Space properties through the API.

It would be nice to have a API endpoint that would return all list or even workspace automations. Something that would return the trigger_id, auto_id and the name of the automation. For teams who are using a lot of automations it is painful to trace back a webhook call and find the CU automation that triggered the webhook. To be able to pull a list of all the automations would also be helpful in cataloging them.

It would be nice to access the inbox and new reminders via the API in the future.

Example scenario: A (non-ClickUp)-form submission automation creates a ClickUp task A confirmation email sent to the submitter A response to the confirmation email should be recorded as a comment (for more details, questions, corrections, etc.)

We utilize a variety of custom fields in our workflows and we are constantly adding options to fields like dropdowns and labels to ensure consistency and "exact match" for some variable items within our project tracking. For Example, "Client Code" is a dropdown to mitigate human error in manual entry. As new clients come online, we can automate MOST of the onboarding process but still need to add these options to the dropdown lists manually. It would sure be swell if this was something we could tie into the automations to create new options automatically.

The integration of ClickUp’s timesheets with external billing platforms, such as OpenEhr, has faced significant challenges due to the lack of API support for timesheet approvals. This limitation has resulted in complex and inefficient workflows, requiring additional development work and support resources to manage frequent issues. Lack of API Support for Timesheet Approvals: Issue: The absence of API endpoints for timesheet approvals prevents seamless integration with billing platforms like OpenEhr. Impact: Changes made in ClickUp are not consistently reflected through the API, leading to discrepancies and delays. Complexity of Integration: Issue: The integration process becomes highly complex without proper API support, requiring extensive development work and a dedicated help desk to address recurring problems. Impact: This complexity has caused significant delays, with users unable to fully utilize ClickUp’s intended functionality for over a year. Proposed Solution: Develop a public API for Timesheet Approvals with the following capabilities: Support for submitting, approving, and managing timesheets via API. Real-time synchronization of changes made in ClickUp with external systems. Webhook notifications for approval events to enhance visibility and reduce delays. This feature is critical to enable seamless integration with billing platforms, reduce operational complexity, and ensure that users can fully leverage ClickUp’s timesheet functionality without incurring unnecessary costs or delays.

The ClickUp API currently supports comments for tasks, lists, and chat views, but there's no endpoint to retrieve comments from documents. This is a significant limitation for teams that rely heavily on document collaboration and need to programmatically access feedback and comments within ClickUp documents.