Task List Response is too big
not on the roadmap
K
Kaushik Vaghasiya
I am using following API with date filters and pagination.
This API returns all task related data and response size is too bing (~20MB per page). Can we please add fields parameter to request only fields that user is interested in. Thank you.
Log In
Autopilot
Merged in a post:
Ability to filter the response body for GET calls on the API
Eric Wightman
Sometimes the number of rows in a GET response (like GET tasks) can cause the call to take longer than expected. Having the ability to filter those results for only data that I need (like task name, assignee, etc) will speed up response times and give me the data that I need.
Autopilot
Merged in a post:
Select the list of fields pulled in the response
Raul Cruz
The current API returns the whole list of fields available for a task. Our integration requires just a handful of attributes.
Implementing this feature would reduce processing times dramatically.
Thanks.
A
API User AE
Joey the post's "inactive" state was from your / Clicup's end. We're "actively" waiting for each and every request on this forum. If you see no activity on a post it is most likely for the sole reason of people "giving up" on seeing activity from CU, not that it is no longer something we need or want.
Joey
marked this post as
not on the roadmap
Hey there! Thanks for sharing your feature request with us. We truly appreciate your input!
As part of our efforts to improve our feedback boards, we're closing this older feature request.
Removing old and inactive posts will increase the communication between the ClickUp team and our users, allowing us to hear more of your great ideas!
If you feel this request is worth revisiting, feel free to create a new post!
Thanks for being a part of our community!
A
API User AE
Great idea.
For starters please get rid of the dropdown definitions/options from the response. The data is redundant and significantly bloats the responses.
One of our lists we have couple hundred dropdown options and couple thousand tasks resulting in getting over THREE MILLION option definitions when we already have the info from a single request to get the fields for the specific list.
Lucas Jans
Please implement something like ?pluck-fields={fieldId}[] - we just get so much unnecessary data via the API right now that slows down the requests.
D
Dylan Bridgman
I have this issue too, especially where custom fields have many options, and would also benefit from being able to request only some fields.
Some responses have been upwards of 40MB.
t
tim castelijn
We use many custom fields, for instance: drowdowns with +100 options. A GET request on a task always returns all custom fields including all their options. This results in a big response for even a single task (see screenshot) and long reponse times.
For API calls this is just inconvenient, but if this mechanism is also used to fetch and display data in the UI, I think it must be adressed to decrease loading times.
I think Eric Wightmans solution; fetching only data that you need - would increase performance a lot.
J
Jason Hatchett
We're specifically looking to filter by priority (or lack thereof) so we can check that certain tickets with a "security" label have a priority. We need a similar filter for find a lack of assignee.