Get tasks from a section

get

https://app.asana.com/api/1.0/sections/{section_gid}/tasks

Required scope: tasks:read

Board view only: Returns the compact section records for all tasks within the given section.

Path Params

section_gid

string

required

The globally unique identifier for the section.

Query Params

opt_fields

array of strings

This endpoint returns a resource which excludes some properties by default. To include those optional properties, set this query parameter to a comma-separated list of the properties you wish to include.

opt_fields

opt_pretty

boolean

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.

limit

integer

1 to 100

Results per page. The number of objects to return per page. The value must be between 1 and 100.

offset

string

Offset token. 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.

completed_since

string

Only return tasks that are either incomplete or that have been completed since this time. Accepts a date-time string or the keyword now.

Responses

Language

Credentials

Request

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200Successfully retrieved the section's tasks.

400This usually occurs because of a missing or malformed parameter. Check the documentation and the syntax of your request and try again.

401A valid authentication token was not provided with the request, so the API could not associate a user with the request.

403The authentication and request syntax was valid but the server is refusing to complete the request. This can happen if you try to read or write to objects or properties that the user does not have access to.

404Either the request method and path supplied do not specify a known action in the API, or the object specified by the request does not exist.

500There was a problem on Asana’s end. In the event of a server error the response body should contain an error phrase. These phrases can be used by Asana support to quickly look up the incident that caused the server error. Some errors are due to server load, and will not supply an error phrase.