Access Token

Refresh Token

Asana

True if the project is archived, false if not. Archived projects do not show in the UI by default and may be treated differently for queries.

True if the project is currently marked complete, false if not.

The time at which this project was completed, or null if the project is not completed.

The user that marked this project complete, or null if the project is not completed.

Globally unique identifier of the resource, as a string.

*Read-only except when same user as requester*. The user’s name.

The time at which this resource was created.

A generic Asana Resource, containing a globally unique identifier.

*Deprecated: new integrations should prefer the `current_status_update` resource.*

The color associated with the status update.

[Opt In](/docs/inputoutput-options). The text content of the status update with formatting as HTML.

The time at which this project status was last modified.
*Note: This does not currently reflect any changes in associations such as comments that may have been added or removed from the project status.*

The latest `status_update` posted to this project.

The subtype of this resource. Different subtypes retain many of the same fields and behavior, but may render differently in Asana or represent resources with different semantic meaning.
The `resource_subtype`s for `status` objects represent the type of their parent.

Array of Custom Field Settings (in compact form).

The default view (list, board, calendar, or timeline) of a project.

*Deprecated: new integrations should prefer the `due_on` field.*

The day on which this project is due. This takes a date with format YYYY-MM-DD.

Array of users following this project. Followers are a subset of members who have opted in to receive "tasks added" notifications for a project.

[Opt In](/docs/inputoutput-options). The notes of the project with formatting as HTML.

Array of users who are members of this project.

The time at which this project was last modified.
*Note: This does not currently reflect any changes in associations such as tasks or comments that may have been added or removed from the project.*

Name of the project. This is generally a short sentence fragment that fits on a line in the UI for maximum readability. However, it can be longer.

Free-form textual information associated with the project (ie., its description).

The current owner of the project, may be null.

A url that points directly to the object within Asana.

True if the project is public to its team.

The day on which work for this project begins, or null if the project has no start date. This takes a date with `YYYY-MM-DD` format. *Note: `due_on` or `due_at` must be present in the request when setting or unsetting the `start_on` parameter. Additionally, `start_on` and `due_on` cannot be the same date.*

Projects

An array of strings identifying users. These can either be the string "me", an email, or the gid of a user.

Name of the tag. This is generally a short sentence fragment that fits on a line in the UI for maximum readability. However, it can be longer.

Free-form textual information associated with the tag (i.e. its description).

Tags

This value represents the sum of all the Time Tracking entries in the Actual Time field on a given Task. It is represented as a nullable long value.

*Conditional* Reflects the approval status of this task. This field is kept in sync with `completed`, meaning `pending` translates to false while `approved`, `rejected`, and `changes_requested` translate to true. If you set completed to true, this field will be set to `approved`.

The name of the section (i.e. the text displayed as the section header).

*Deprecated* Scheduling status of this task for the user it is assigned to. This field can only be set if the assignee is non-null. Setting this field to "inbox" or "upcoming" inserts it at the top of the section, while the other options will insert at the bottom.

True if the task is currently marked complete, false if not.

The time at which this task was completed, or null if the task is incomplete.

[Opt In](/docs/inputoutput-options). Array of resources referencing tasks that this task depends on. The objects contain only the gid of the dependency.

[Opt In](/docs/inputoutput-options). Array of resources referencing tasks that depend on this task. The objects contain only the ID of the dependent.

The UTC date and time on which this task is due, or null if the task has no due time. This takes an ISO 8601 date string in UTC and should not be used together with `due_on`.

The localized date on which this task is due, or null if the task has no due date. This takes a date with `YYYY-MM-DD` format and should not be used together with `due_at`.

*OAuth Required*. *Conditional*. This field is returned only if external values are set or included by using [Opt In] (/docs/inputoutput-options).
The external field allows you to store app-specific metadata on tasks, including a gid that can be used to retrieve tasks and a data blob that can store app-specific character strings. Note that you will need to authenticate with Oauth to access or modify this data. Once an external gid is set, you can use the notation `external:custom_gid` to reference your object anywhere in the API where you may use the original object gid. See the page on Custom External Data for more details.

*Create-Only* An array of strings identifying users. These can either be the string "me", an email, or the gid of a user. In order to change followers on an existing task use `addFollowers` and `removeFollowers`.

*Deprecated - please use liked instead* True if the task is hearted by the authorized user, false if not.

*Deprecated - please use likes instead* Array of likes for users who have hearted this task.

[Opt In](/docs/inputoutput-options). The notes of the text with formatting as HTML.

[Opt In](/docs/inputoutput-options). In some contexts tasks can be rendered as a visual separator; for instance, subtasks can appear similar to [sections](/reference/sections) without being true `section` objects. If a `task` object is rendered this way in any context it will have the property `is_rendered_as_separator` set to `true`.

True if the task is liked by the authorized user, false if not.

Array of likes for users who have liked this task.

*Create-only*. Array of projects this task is associated with and the section it is in. At task creation time, this array can be used to add the task to specific sections. After task creation, these associations can be modified using the `addProject` and `removeProject` endpoints. Note that over time, more types of memberships may be added to this property.

The time at which this task was last modified.

*Note: This does not currently reflect any changes in
associations such as projects or comments that may have been
added or removed from the task.*

Free-form textual information associated with the task (i.e. its description).

*Deprecated - please use likes instead* The number of users who have hearted this task.

The number of users who have liked this task.

[Opt In](/docs/inputoutput-options). The number of subtasks on this task.


The subtype of this resource. Different subtypes retain many of the same fields and behavior, but may render differently in Asana or represent resources with different semantic meaning.
The resource_subtype `milestone` represent a single moment in time. This means tasks with this subtype cannot have a start_date.

Date and time on which work begins for the task, or null if the task has no start time. This takes an ISO 8601 date string in UTC and should not be used together with `start_on`.
*Note: `due_at` must be present in the request when setting or unsetting the `start_at` parameter.*

The day on which work begins for the task , or null if the task has no start date. This takes a date with `YYYY-MM-DD` format and should not be used together with `start_at`.
*Note: `due_on` or `due_at` must be present in the request when setting or unsetting the `start_on` parameter.*

Tasks

Controls who can edit team name and description


Controls who can edit team visibility and trash teams


Controls who can accept or deny guest invites for a given team


The description of the team with formatting as HTML.


Controls who can accept or deny join team requests for a Membership by Request team


Controls who can accept or deny member invites for a given team


The visibility of the team to users in the same organization


Teams

A map of the user’s profile photo in various sizes, or null if no photo is set. Sizes provided are 21, 27, 36, 60, 128, and 1024. All images are in PNG format, except for 1024 (which is in JPEG format).

A string identifying a user. This can either be the string "me", an email, or the gid of a user.

Workspaces and organizations this user may access.
Note\: The API will only return workspaces and organizations that also contain the authenticated user.

Users

The email domains that are associated with this workspace.

Whether the workspace is an *organization*.

	Tasks automatically maps to	Users automatically maps to	Projects automatically maps to
Jira	Issues	Users	Projects
Clickup	Tasks	Workspace Users	Lists
Teamleader	Tasks	Users	Projects
Zoho Books	Tasks	Users	Projects
Basecamp	—	People	Projects
Github	Issues	Users	—
Trello Connector	Cards	—	Boards
Zendesk	Tickets	Users	—
Salesloft	Tasks	Users	—
Copper	Tasks	Users	—

Asana API Integration Profile

Getting Started

Data Collections

Use the same code to integrate with Asana and 100+ other applications

Tasks

Users

Projects

Get better integration infrastructure for your SaaS product today.

	List	Find by Id	Search	Create	Update	Delete
Projects
Tasks
Tags
Teams
Workspaces

Asana API Integration Profile

Getting Started

Data Collections

Use the same code to integrate with Asana and 100+ other applicationsself.__wrap_n!=1&&self.__wrap_b(":Rb5t56:",1)

Tasks

Users

Projects

Get better integration infrastructure for your SaaS product today.

Use the same code to integrate with Asana and 100+ other applications