Public API

It would be great to have the option to create apps and authenticate with client Credential Oauth Flow. That would be much more secure and robust way to connect to our landscapes

Model Context Protocol (MCP) is basically a must-have feature for all SaaS now. ClickUp providing an official, first-party server would allow users to interact with ClickUp API directly through their agentic AI tool of choice (Claude, GitHub Copilot, Cursor, etc.) https://modelcontextprotocol.io/introduction Most of ClickUp's competitors already offer their own first-party, official MCP server. ClickUp is falling behind in this space, unless it is just not announced yet. Several people have created unofficial ClickUp MCP servers, but they are never going to be as good as what a first-party server could provide. Note: This is not related to MCP support in ClickUp AI ( https://feedback.clickup.com/feature-requests/p/support-mcp-model-context-protocol-in-clickup-ai ), which is requesting support for other provider's servers in ClickUp.

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.

Allow the definition of a space's standard work week and holidays, AND allow for each user to set their own working hours and holidays. This solves part time workers, shift work, different cultural requirements, etcetera without having to build templates or rules to offer each as it's own option. Just let US build what we do/don't work as team and individuals. I tried looking for this, but I have seen a TON of different versions of this: 6 days work weeks for all, 4x10 for some, some of each in the same space, etc. I have seen people ask for better holiday control per person, or per work, but I think they all boil down to the same idea: let US set up the working days and times on a per space or per person basis and it will solve about a dozen requests or more.

An endpoint to fetch all tasks that are linked to another task by ID

Currently we have 3 cases: the Archived flag is not passed - This returns only non-archived elements archived=false - This returns only non-archived elements archived=true - This returns only archived elements It would be nice to have the possibility to get both statuses with one call

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.)

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.

Change the status of a user via API