Public API

Now with the new update of being able to write in rich text for the custom field for long text. It is a necessity to be able to access this through the API!

The current ClickUp API response for time entries lacks critical indicators to distinguish between how time was logged: Direct Task Tracking: Time entries logged directly on tasks use the local time as the end time when the timer is stopped. Timesheet Logging: Retrospective time entries logged via the Timesheet feature use the local time as the start time. This creates significant ambiguity in the data retrieved from the Get Time Entries API ( https://clickup.com/api/clickupreference/operation/Gettimeentrieswithinadaterange/ ). Specifically, there is no clear way to determine the exact date to which a time entry should be attributed. While start and end timestamps are provided, they can span multiple days, and there is no indication of the intended date for the logged hours. Impact on Reports and Business Processes: Payroll calculations. Public holiday or overtime tracking. Compliance with labor regulations. For example, if an employee logs time across days, incorrect handling of start/end times might count hours toward the wrong date, resulting in potential underpayment or misclassification of hours.

There is a need for a time-tracked date field by task. I can't use start date and duration columns because if the duration exceeds 24 hours, I will have only 1 start date for this task. Instead, I would like to have 2 dates/rows for this task with a duration breakdown for each date.

We are currently storing customer names in a custom field. We would like to retrieve any custom fields associated with tasks that have corresponding time entries. The response already includes the taskID; we just need the custom fields to be included in the response as well. The ideal solution would be to introduce an additional query parameter, allowing us to specify which custom fields should be returned. This would be similar to other API calls where the custom field ID is used to filter the returned data. API Call to Update: https://clickup.com/api/clickupreference/operation/Gettimeentrieswithinadaterange/ Example API Call using query parameters: https://clickup.com/api/clickupreference/operation/GetTasks/#tag/Tasks/operation/GetTasks!in=query&path=custom_fields&t=request

Hi ClickUp Team, this is a real problem which you can hopefully solve fast and easy: Currently Time Tracking GET API ( https://clickup.com/api/clickupreference/operation/Gettimeentrieswithinadaterange/ ) does not allow to filter by Tags. As Time Tracking Entries don't have status yet (billed, unbilled, pending, ...) which is a separate issue, like many other CU users we're using Tags in Time Tracking entries to set what has been "billed". To be able to create invoices based on this, we created an app which fetches the time entries to be billed. Sadly there's no other way then fetching ALL (ten thousands) time entries and filtering the results in the client. This is really annoying. Could you please allow to filter for (HAS / HAS NOT) tags until statuses are available for Time entries? That would be super helpful.

In the UI, you can see the rollup of the children's time estimate and time tracked. I would like to have that available in the API without having to retrieve the children and sum them on my end.

The labels and dropdown custom field type should display the value of the field, not its id, in the API response

It doesn't looks its possible to archive a list through the API. This would be handy.