# GraphQL

**URL:** <https://forum.asana.com/t/graphql/45822>\
**Category:** API & Developers\
**Created:** [28 March 2019 15:57 UTC](https://forum.asana.com/t/graphql/45822 "2019-03-28T15:57:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andrew\_Szeto](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/andrew_szeto/32/29878_2.png) [@Andrew\_Szeto](https://forum.asana.com/u/Andrew_Szeto)\
**Post date:** [28 March 2019 15:57 UTC](https://forum.asana.com/t/graphql/45822/1 "2019-03-28T15:57:56Z")

</div>

I read in [Get all Tasks(Tasks,SubTasks, Sub-SubTasks) together - #4 by Matt\_Bramlage](https://forum.asana.com/t/get-all-tasks-tasks-subtasks-sub-subtasks-together/10979/4) that GraphQL support was possible / in the works. Is there any update to this?

---

<div class="post-metadata">

**Author:** ![Ross\_Grambo](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/ross_grambo/32/68568_2.png) [@Ross\_Grambo](https://forum.asana.com/u/Ross_Grambo)\
**Post date:** [28 March 2019 22:12 UTC](https://forum.asana.com/t/graphql/45822/2 "2019-03-28T22:12:10Z")

</div>

Hello @Andrew_Szeto!

We have talked about this and continue to do so, but currently nothing is in the works to add GraphQL support.

Also, the method described in this comment is currently being deprecated so I would advise against using it as well. ( see [The `subtasks` field on tasks is being deprecated](https://forum.asana.com/t/the-subtasks-field-on-tasks-is-being-deprecated/44548) ).

If we keep hearing requests for this functionality, hopefully it will be on the roadmap soon.

Best,  
Ross

---

<div class="post-metadata">

**Author:** ![Andrew\_Szeto](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/andrew_szeto/32/29878_2.png) [@Andrew\_Szeto](https://forum.asana.com/u/Andrew_Szeto)\
**Post date:** [28 March 2019 23:47 UTC](https://forum.asana.com/t/graphql/45822/3 "2019-03-28T23:47:42Z")

</div>

GraphQL would be good for specifically this bug regarding infinite expansion of subtasks because queries would have to explicitly request the amount of nesting they want in the response. The [spec](https://graphql.github.io/graphql-spec/June2018/#sec-Fragment-spreads-must-not-form-cycles) itself forbids cycles in requests.

---

<div class="post-metadata">

**Author:** ![Joe\_Trollo](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/joe_trollo/32/4025_2.png) [@Joe\_Trollo](https://forum.asana.com/u/Joe_Trollo)\
**Post date:** [4 April 2019 19:37 UTC](https://forum.asana.com/t/graphql/45822/4 "2019-04-04T19:37:34Z")

</div>

Hi @Andrew_Szeto, GraphQL unfortunately would not solve the subtasks issue. Even limiting nesting to just one or two levels of subtasks can still load enough data from our databases for one API request to cause stability issues.

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/system/32/276370_2.png) [@system](https://forum.asana.com/u/system)\
**Post date:** [30 May 2025 19:00 UTC](https://forum.asana.com/t/graphql/45822/5 "2025-05-30T19:00:30Z")

</div>

Closed on 30 May 2025 19:00 UTC