Back to Asana
Get Dependencies From A Task
Returns the compact representations of all of the dependencies of a task.
description: The task to operate on.
Provides “pretty” output.
Provides the response in a “pretty” format. In the case of JSON this
means doing proper line breaking and indentation to make it readable.
This will take extra time and increase the response size so it is
advisable only to use this during debugging.
Defines fields to return.
Some requests return *compact* representations of objects in order to
conserve resources and complete the request more efficiently. Other
times requests return more information than you may need. This option
allows you to list the exact set of fields that the API should be sure
to return for the objects. The field names should be provided as
paths, described below.
The id of included objects will always be returned, regardless of the
Results per page.
The number of objects to return per page. The value must be between 1
An offset to the next page returned by the API. A pagination request
will return an offset token, which can be used as an input parameter
to the next request. If an offset is not passed in, the API will
return the first page of results.
'Note: You can only pass in an offset that was returned to you via a
previously paginated request.'
description: Globally unique identifier of the resource, as a string.
description: The base type of this resource.
description: The name of the task.
example: Bug 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.