# Avaliable Optional Fields for Tasks

**URL:** <https://forum.asana.com/t/avaliable-optional-fields-for-tasks/163084>\
**Category:** API & Developers\
**Tags:** tasks\
**Created:** [28 April 2022 16:23 UTC](https://forum.asana.com/t/avaliable-optional-fields-for-tasks/163084 "2022-04-28T16:23:38Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![anon19201745](https://luna1.co/8d76cd.png) [@anon19201745](https://forum.asana.com/u/anon19201745)\
**Post date:** [28 April 2022 16:23 UTC](https://forum.asana.com/t/avaliable-optional-fields-for-tasks/163084/1 "2022-04-28T16:23:38Z")

</div>

Hello!

I am trying to figure out where a list of all the optional fields are for a Task. I have been using the `opt_fields` to add several fields as I’ve found them through trial and error. But I have yet to find an actual list of fields I could choose to pull down, it doesn’t appear to exist in the Task API documentation at all.

[This part](https://developers.asana.com/docs/input-output-options) of the docs explains _how_ to do it, but not what’s available. When I just pull down Tasks without specifing any fields it only gives me `gid`, `name`, and `resource_type`.

If it helps I would like to see if there is an `added_at` date for a task. I.E. if I add a Task to one project, and then 5 days later I add it to another project is there some way for me to know the exact date it was added?

Thanks!

---

<div class="post-metadata">

**Author:** ![Frederic\_Malenfant](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/frederic_malenfant/32/8358_2.png) [@Frederic\_Malenfant](https://forum.asana.com/u/Frederic_Malenfant)\
**Post date:** [28 April 2022 19:40 UTC](https://forum.asana.com/t/avaliable-optional-fields-for-tasks/163084/2 "2022-04-28T19:40:53Z")

</div>

Hi @anon19201745 , welcome to the forum!

I know that there’s a hidden place somewhere in the API where the “schema” of objects are documented, but I never remember where.

What I personnaly do to get the list of available fields, is to query one single item, example

GET /tasks/xyz

Then, looking at the result, I have a good idea which opt\_fields I can use when I query a list of tasks, based on that single task.

Also, you can add opt\_fields of subItems using the “dot”, example:

opt\_fields=“name,due\_at,due\_on,memberships.project.name,attachments.created\_at, …”

---

<div class="post-metadata">

**Author:** ![Bastien\_Siebman](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/bastien_siebman/32/172354_2.png) [@Bastien\_Siebman](https://forum.asana.com/u/Bastien_Siebman)\
**Post date:** [29 April 2022 05:37 UTC](https://forum.asana.com/t/avaliable-optional-fields-for-tasks/163084/3 "2022-04-29T05:37:11Z")

</div>

> [@Frederic\_Malenfant](#):
>
> I know that there’s a hidden place somewhere in the API where the “schema” of objects are documented, but I never remember where.

[Bottom of the sidebar](https://developers.asana.com/docs) 🙂

I do the same thing as @Frederic_Malenfant , querying a task to get a list of available fields.

---

<div class="post-metadata">

**Author:** ![anon19201745](https://luna1.co/8d76cd.png) [@anon19201745](https://forum.asana.com/u/anon19201745)\
**Post date:** [29 April 2022 14:05 UTC](https://forum.asana.com/t/avaliable-optional-fields-for-tasks/163084/4 "2022-04-29T14:05:09Z")

</div>

Oh man, thank you @Frederic_Malenfant and @Bastien_Siebman!

I see it now, the schema looks to be under:

> **[Tasks](https://developers.asana.com/reference/tasks)**
>
> The task is the basic object around which many operations in Asana are centered. In the Asana application, multiple tasks populate the middle pane according to some view parameters, and the set of selected tasks determines the more detailed...

Whereas the API’s are under:

> **[Tasks](https://developers.asana.com/reference/tasks)**
>
> The task is the basic object around which many operations in Asana are centered. In the Asana application, multiple tasks populate the middle pane according to some view parameters, and the set of selected tasks determines the more detailed...

But I will definitely use that other trick as well! 🙂

If anyone who works on the docs sees this it would be really nice if the schema was linked under this part of the docs:  
`See Input/Output Options to include more fields in your response.`

---

<div class="post-metadata">

**Author:** ![Bastien\_Siebman](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/bastien_siebman/32/172354_2.png) [@Bastien\_Siebman](https://forum.asana.com/u/Bastien_Siebman)\
**Post date:** [30 April 2022 05:09 UTC](https://forum.asana.com/t/avaliable-optional-fields-for-tasks/163084/5 "2022-04-30T05:09:38Z")

</div>

It took me about 5 years to realise there were schemas there 🤦‍♂️

---

<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 18:54 UTC](https://forum.asana.com/t/avaliable-optional-fields-for-tasks/163084/6 "2025-05-30T18:54:51Z")

</div>

Closed on 30 May 2025 18:54 UTC


