Hi everyone, To increase the speed and stability of the API, we are transitioning to a world with fewer non-paginated fields. Deprecations are never fun. Thankfully, this one only affects a small number of apps and we’ve built a workaround that will be useful for many more Asana developers. What’…

Just received the email about this change. Our organization uses subtasks heavily, and we’re using the API to visualize them. If I understand this change, it means that what we’ve been doing in one request (grabbing all tasks and their immediate subtasks) is going to become 40-50 requests. Is that …

Our customers at Everhour also use subtasks a lot. Everhour provides time tracking possibilities for Asana tasks and subtasks. But now it will require us do much more requests to sync all project tasks. Do you have alternative option API to get all project tasks & subtasks?

Hi @Brian_Victor , you are correct that it will require more API calls to get all of the subtasks in a project. Without knowing your exact workflow and how deep your subtasks go, I’m not certain how many more requests it will take. While it was never meant to be supported, you can currently get all…

Hi @Yury , Thanks for reaching out and sorry that we have to make this change. The new approach for getting all tasks and subtasks in a project using the num_subtasks field instead of subtasks is actually not that different. We have always required pagination, we are now just also requiring it for …

@Jeff_Schneider I was asking about events as a way to avoid polling the entire project just to see if anything had changed. From what you say, it appears they might work for that. It would still be nice to have a push mechanism. (Webhooks seem to require running a server and forwarding the pushes to…

@Brian_Victor As you point out, we have two options for getting changes: Poll for events on a project, task or subtask (note: that events bubble up, so changes to tasks or subtasks would trigger events on a project). Get events sent to you with webhooks. Webhooks do add complexity and require tha…

You want to avoid flattened task requests even with pagination and perhaps depth limits? I understand not wanting unbounded responses, but I feel like there must be a way to avoid that without also requiring an explosion of requests. I’m happy to explore ideas with you if you’re open to looking for …

Hi, we are using lot of these “hidden undocumented sub-queries”, because we don’t know from the root if the container have or not subitems. This new num_subtasks field is totally welcome. May I suggest to also add num_attachments num_(any-subitem-that-require-additional-query)!

I just found an issue… if I query my task using opt_fields parameter, I can get this new field. But, it is not included in the default fields, if I query my task without parameters, like this: GET https://app.asana.com/api/1.1/tasks/xxxxxxx I have num_hearts, num_likes, but no num_subtasks.

[image] Frederic_Malenfant: if I query my task using opt_fields parameter, I can get this new field. But, it is not included in the default fields This is “as designed” - the num_subtasks field is documented as an opt-in field requiring that you ask for it.

The `subtasks` field on tasks is being deprecated

Asana Community API & Developers

Topic		Replies	Views
You can now see and action subtasks directly from your Project task list! Product Updates	62	24928	23 December 2020
Problems with Asana API rate limitations when accessing sub-tasks API & Developers subtasks , api	10	3615	12 February 2019
Get all Tasks(Tasks,SubTasks, Sub-SubTasks) together API & Developers	13	6699	2 March 2020
Subtasks now show parent project and fields in the task pane ✨ Product Updates	79	3894	6 August 2026
Subtasks Cheat Sheet: What you need to know Forum Leader tips subtasks , forum-leader-tip	25	9017	13 March 2024

The `subtasks` field on tasks is being deprecated

Related topics