# Problems with Asana API rate limitations when accessing sub-tasks

**URL:** <https://forum.asana.com/t/problems-with-asana-api-rate-limitations-when-accessing-sub-tasks/39784>\
**Category:** API & Developers\
**Tags:** api, subtasks\
**Created:** [18 January 2019 15:25 UTC](https://forum.asana.com/t/problems-with-asana-api-rate-limitations-when-accessing-sub-tasks/39784 "2019-01-18T15:25:02Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Phil\_Seeman](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/phil_seeman/32/81525_2.png) [@Phil\_Seeman](https://forum.asana.com/u/Phil_Seeman)\
**Post date:** [18 January 2019 20:29 UTC](https://forum.asana.com/t/problems-with-asana-api-rate-limitations-when-accessing-sub-tasks/39784/4 "2019-01-18T20:29:19Z")

</div>

@Frederic_Malenfant, @Christoph,

Yes, I knew about (and used to use) the method that Frederic describes; but I didn’t mention it in my reply to Christoph because it’s not officially supported and Asana does not want us to use it - see:

> [@Enable to fetch sub-task details without task id](https://forum.asana.com/t/enable-to-fetch-sub-task-details-without-task-id/26663/3):
>
> Accessing subtasks as attributes of a task by using opt\_expand=subtasks or similar is not officially supported in the API because it frequently causes stability issues. The only supported way to fetch the subtasks of a task is to call GET /tasks/task-id/subtasks. We’re aware that fetching all subtasks in this way is painful, and we are thinking about additional alternatives that would be easier to use.

---

_[View the full topic](https://forum.asana.com/t/problems-with-asana-api-rate-limitations-when-accessing-sub-tasks/39784)._