GET /workspaces/{workspace_gid}/projects/search
Required scope: projects:read
To mirror the functionality of the Asana web app's advanced search feature, the Asana API has a project search endpoint that allows you to build complex filters to find and retrieve the exact data you need.
Premium access
Like the Asana web product's advance search feature, this search endpoint will only be available to premium Asana users. A user is premium if any of the following is true:
- The workspace in which the search is being performed is a premium workspace - The user is a member of a premium team inside the workspace
Even if a user is only a member of a premium team inside a non-premium workspace, search will allow them to find data anywhere in the workspace, not just inside the premium team. Making a search request using credentials of a non-premium user will result in a 402 Payment Required error.
Pagination
Search results are not stable; repeating the same query multiple times may return the data in a different order, even if the data do not change. Because of this, the traditional pagination available elsewhere in the Asana API is not available here. However, you can paginate manually by sorting the search results by their creation time and then modifying each subsequent query to exclude data you have already seen. Page sizes are limited to a maximum of 100 items, and can be specified by the limit query parameter.
Eventual consistency
Changes in Asana (regardless of whether they’re made though the web product or the API) are forwarded to our search infrastructure to be indexed. This process can take between 10 and 60 seconds to complete under normal operation, and longer during some production incidents. Making a change to a project that would alter its presence in a particular search query will not be reflected immediately. This is also true of the advanced search feature in the web product. Because of this delay, the search endpoint is not suited for use cases that require immediate consistency after writes. If you need read-your-write behavior or strongly consistent results, we recommend using Get multiple projects instead.
Rate limits
You may receive a 429 Too Many Requests response if you hit any of our rate limits.
Custom field parameters
| Parameter name | Custom field type | Accepted type |
|---|---|---|
| custom_fields.{gid}.is_set | All | Boolean |
| custom_fields.{gid}.value | Text | String |
| custom_fields.{gid}.value | Number | Number |
| custom_fields.{gid}.value | Enum | Enum option ID |
| custom_fields.{gid}.starts_with | Text only | String |
| custom_fields.{gid}.ends_with | Text only | String |
| custom_fields.{gid}.contains | Text only | String |
| custom_fields.{gid}.less_than | Number only | Number |
| custom_fields.{gid}.greater_than | Number only | Number |
For example, if the gid of the custom field is 12345, the query parameter to find projects where it is set would be custom_fields.12345.is_set=true. To match an exact value for an enum custom field, use the gid of the desired enum option and not the name of the enum option: custom_fields.12345.value=67890.
Not Supported: searching for multiple exact matches of a custom field, searching for multi-enum custom field
Servers
- https://app.asana.com/api/1.0
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
workspace_gid |
String | Yes |
Globally unique identifier for the workspace or organization. |
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
completed_on.before |
String | No |
ISO 8601 date string. |
members.not |
String | No |
Comma-separated list of user identifiers to exclude as members. |
sort_ascending |
Boolean | No |
Default Default value: false |
created_on.after |
String | No |
ISO 8601 date string. |
text |
String | No |
Performs full-text search on the project name. |
start_on.after |
String | No |
ISO 8601 date string. |
portfolios.any |
String | No |
Comma-separated list of portfolio IDs to filter on. |
owner.any |
String | No |
Comma-separated list of user identifiers to filter on as project owners. |
sort_by |
String | No |
One of Valid values:
Default value: "modified_at" |
completed_on |
String | No |
ISO 8601 date string or |
created_on.before |
String | No |
ISO 8601 date string. |
completed |
Boolean | No |
Filter on project completion status. |
opt_pretty |
Boolean | No |
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. |
created_at.before |
String | No |
ISO 8601 datetime string. |
completed_on.after |
String | No |
ISO 8601 date string. |
created_on |
String | No |
ISO 8601 date string or |
teams.any |
String | No |
Comma-separated list of team IDs. |
completed_at.before |
String | No |
ISO 8601 datetime string. |
completed_at.after |
String | No |
ISO 8601 datetime string. |
due_at.before |
String | No |
ISO 8601 datetime string. |
start_on |
String | No |
ISO 8601 date string or |
created_at.after |
String | No |
ISO 8601 datetime string. |
due_at.after |
String | No |
ISO 8601 datetime string. |
due_on.after |
String | No |
ISO 8601 date string. |
members.any |
String | No |
Comma-separated list of user identifiers to filter on as members. |
due_on.before |
String | No |
ISO 8601 date string. |
due_on |
String | No |
ISO 8601 date string or |
opt_fields[] |
Array | No |
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. |
start_on.before |
String | No |
ISO 8601 date string. |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.