Public API

Would be epic to have a single text-doc API reference document for all endpoints, explanations, and examples. Yes there is a webpage exist, but we cannot feed that into LLMs easily :) Image we can just teach an AI bot to run our API works for us? Wouldn't be great?

API keys are still apparently tied to the user that created it. This generates a problem to custom applications if lists are not shared to that user. For example, trying to get a task with /api/v2/team/{self.workspace_id}/task will give you a [{'err': 'You do not have access to this list', 'ECODE': 'ACCESS_078'}] error message. Reminding users to always add the "Admin" account to their private lists doesn't sound like a sustainable solution as users can make mistakes and this may lead to inconsistent output in the custom apps that get data from the APIs

Allow a team API token to be generated for integrations. This is to prevent loss of work if ever a user integrates anything and has to leave.

Sometimes the only thing I need from an API token is to read a few things. Especially if the token is going into a shared environment of some kind - Having a read-only / no-op token is important.

GraphQL is a common API language that would be useful to add syntax highlighting for. My team often sketches out our API in the planning phase before we begin coding and it would be great to have syntax highlighting support since we do this planning in ClickUp Docs.

While making an API document, all the request and response are in JSON format, I have to Select language as JSON each and every time. So there should be an option to set language as default.

Currently, the timeout of the clickup custom cloud command waiting for a response from the URL endpoint is 10 seconds. But our endpoint takes more than 10 seconds to complete the execution, so we need an option in the Clickup cloud command to adjust the timeout duration.

As ClickUp continues to grow and more teams develop against the API, it would be a really great feature for Admins in a Workspace to be able to see API request rate numbers. This way it's easily understood whether or not an integration is in danger of reaching the plan's limit (thus necessitating a plan upgrade)