Everything is so slow and takes a long time for even a page to load.

We currently use the API to integrate ClickUp with custom enterprise software systems and databases. Currently, the API actions have to be performed under a user account so all of these automated actions appear to be from a single user. It would be useful for the workspace owner to be able to generate an API Key where the actions are shown to be performed by an API Bot, similar to how automations show that they are performed by ClickBot.

Currently when downloading comments using API, you can download URLs of images that are embedded in the comment itself, but this is no longer possible when image is uploaded as a file. It would make a life easier when you can fetch all URLs of images from the comments no matter the origin.

Increasing "/v1/csv/[workspace id]/import" payload limit from 2MB to 10MB would be key for easier and faster task importing. Having to split a mere 3000-line 1MB csv into 5 different imports is very time-consuming (a 3000-line 1MB csv turns into a 8,9MB payload during import).

Related to https://api.clickup.com/api/v2/task/abcdef/comment API endpoint. Allow using markdown syntax (tables, h1, embedded images etc) while adding a comment to a task. It is possible to use markdown with markdown_content paragraph while creating a new task. I would expect the same behaviour for comments.

ability to get or set Custom task types via API

We'd like the ability to access deleted tasks via the ClickUpAPI, or have an attribute that details if the task was deleted from the front end.

When using the API to get the custom date fields of a task they're returned as 04:00 in the local time of the user making the edit . This would be fine for us except there is no recording of the users local time, or even which user was the last to update a field. We have users all around the world and when a user in a time zone with offset greater than UTC+0400 updates a task the "date" part of the date field is shifted back a day. For example: If a user in Auckland New Zealand selects Nov 5th, 2023 ("2023-11-05") in a date field the API returns Nov 4th, 2023 ("2023-11-04T15:00:00.000Z", after being converted from the Unix timestamp). We have no means of reliably recovering the actual date that was selected. It would be trivial to recover the actually selected date if we had the time zone of the user that updated the info.

A webhook has been established for task-related events such as task creation, task updates, and task comment postings. However, there is an issue where the webhook endpoint is being triggered multiple times upon task creation. I need guidance in resolving this issue. Thank you.

I just tried to create a new sprint folder and set the first sprint on the same index as our other sprints (Sprint 15 for 31/07/23 to 12/08/23) but ClickUp won't let me choose to start on Sprint 15, I'm forced to start on Sprint 1. I had to duplicate another sprint folder without the tasks to get what I want. I don't understand why it was possible before and not anymore. It is useful, we need this feature.