large_5_Burger-Kings-expansion-1024x768.jpg

medium_5_Burger-Kings-expansion-1024x768.jpg

small_5_Burger-Kings-expansion-1024x768.jpg

thumbnail_5_Burger-Kings-expansion-1024x768.jpg

5_Burger-Kings-expansion-1024x768.jpg

Learn how Wavin connected with their end-customers via a branded loyalty app and grew their user base 17x in the first 6 months.

medium_AkzoNobel.png

small_AkzoNobel.png

thumbnail_AkzoNobel.png

AkzoNobel.png

Connect your loyalty program in Asana without researching its API, registering in a developer program, and getting your application approved. We take care of authentication, secure credentials storage, and token refreshes so you don't have to.

Asana

Custom fields are associated with portfolios by way of custom field settings. This method creates a setting for the portfolio.

Add a custom field to a portfolio

Custom fields are associated with projects by way of custom field settings. This method creates a setting for the project.

Add a custom field to a project

Marks a set of tasks as dependencies of this task, if they are not already dependencies. A task can have at most 30 dependents and dependencies combined.

Set dependencies for a task

Marks a set of tasks as dependents of this task, if they are not already dependents. A task can have at most 30 dependents and dependencies combined.

Set dependents for a task

Adds the specified list of users as followers to the project. Followers are a subset of members who have opted in to receive "tasks added" notifications for a project. Therefore, if the users are not already members of the project, they will also become members as a result of this operation.
Returns the updated project record.

Add followers to a project

Adds followers to a task. Returns an empty data block.
Each task can be associated with zero or more followers in the system.
Requests to add/remove followers, if successful, will return the complete updated task record, described above.

Add followers to a task

Adds followers to a goal. Returns the goal the followers were added to.
Each goal can be associated with zero or more followers in the system.
Requests to add/remove followers, if successful, will return the complete updated goal record, described above.

Add a collaborator to a goal

Add an item to a portfolio.
Returns an empty data block.

Add a portfolio item

Adds the specified list of users as members of the portfolio.
Returns the updated portfolio record.

Add users to a portfolio

Adds the specified list of users as members of the project. Note that a user being added as a member may also be added as a *follower* as a result of this operation. This is because the user's default notification settings (i.e., in the "Notifcations" tab of "My Profile Settings") will override this endpoint's default behavior of setting "Tasks added" notifications to `false`.
Returns the updated project record.

Add users to a project

Adds the task to the specified project, in the optional location
specified. If no location arguments are given, the task will be added to
the end of the project.

`addProject` can also be used to reorder a task within a project or
section that already contains it.

At most one of `insert_before`, `insert_after`, or `section` should be
specified. Inserting into a section in an non-order-dependent way can be
done by specifying section, otherwise, to insert within a section in a
particular place, specify `insert_before` or `insert_after` and a task
within the section to anchor the position of this task.

Returns an empty data block.

Add a project to a task

Creates a goal relationship by adding a supporting resource to a given goal.

Returns the newly created goal relationship record.

Add a supporting goal relationship

Adds a tag to a task. Returns an empty data block.

Add a tag to a task

Add a task to a specific, existing section. This will remove the task from other sections of the project.

The task will be inserted at the top of a section unless an insert_before or insert_after parameter is declared.

This does not work for separators (tasks with the resource_subtype of section).

Add task to section

The user making this call must be a member of the team in order to add others. The user being added must exist in the same organization as the team.

Returns the complete team membership record for the newly added user.

Add a user to a team

Add a user to a workspace or organization.
The user can be referenced by their globally unique user ID or their email address. Returns the full user record for the invited user.

Add a user to a workspace or organization

Upload an attachment.

This method uploads an attachment on an object and returns the compact
record for the created attachment object. This is possible by either:

- Providing the URL of the external resource being attached, or
- Downloading the file content first and then uploading it as any other attachment. Note that it is not possible to attach
files from third party services such as Dropbox, Box, Vimeo & Google Drive via the API

The 100MB size limit on attachments in Asana is enforced on this endpoint.

This endpoint expects a multipart/form-data encoded request containing the full contents of the file to be uploaded.

Requests made should follow the HTTP/1.1 specification that line
terminators are of the form `CRLF` or `\r\n` outlined
[here](http://www.w3.org/Protocols/HTTP/1.1/draft-ietf-http-v11-spec-01#Basic-Rules) in order for the server to reliably and properly handle the request.

Upload an attachment

Make multiple requests in parallel to Asana's API.

Submit parallel requests

Creates a new custom field in a workspace. Every custom field is required
to be created in a specific workspace, and this workspace cannot be
changed once set.

A custom field’s name must be unique within a workspace and not conflict
with names of existing task properties such as `Due Date` or `Assignee`.
A custom field’s type must be one of `text`, `enum`, `multi_enum`, `number`,
`date`, or `people`.

Returns the full record of the newly created custom field.

Create a custom field

Creates an enum option and adds it to this custom field’s list of enum options. A custom field can have at most 500 enum options (including disabled options). By default new enum options are inserted at the end of a custom field’s list.
Locked custom fields can only have enum options added by the user who locked the field.
Returns the full record of the newly created enum option.

Create an enum option

Creates and adds a goal metric to a specified goal. Note that this replaces an existing goal metric if one already exists.

Create a goal metric

Creates a new goal in a workspace or team.

Returns the full record of the newly created goal.

Create a goal

Creates a new membership in a `team`, `project`, `goal`, or `portfolio`.
`Teams` or `users` can be a member of `goals`. `Project`, `team`, and
`portfolios` have users as members.

Returns the full record of the newly created membership.

Create a membership

This method creates a request to export an Organization. Asana will complete the export at some point after you create the request.

Create an organization export request

Creates a new portfolio in the given workspace with the supplied name.

Note that portfolios created in the Asana UI may have some state
(like the “Priority” custom field) which is automatically added
to the portfolio when it is created. Portfolios created via our
API will *not* be created with the same initial state to allow
integrations to create their own starting state on a portfolio.

Create a portfolio

Creates a new project brief.

Returns the full record of the newly created project brief.

Create a project brief

Creates a project shared with the given team.

Returns the full record of the newly created project.

Create a project in a team

Creates a project in the workspace.

If the workspace for your project is an organization, you must also
supply a team to share the project with.

Returns the full record of the newly created project.

Create a project in a workspace

*Deprecated: new integrations should prefer the `/status_updates` route.*

Creates a new status update on the project.

Returns the full record of the newly created project status update.

Create a project status

Create a new project in a workspace or team.

Every project is required to be created in a specific workspace or
organization, and this cannot be changed once set. Note that you can use
the `workspace` parameter regardless of whether or not it is an
organization.

If the workspace for your project is an organization, you must also
supply a `team` to share the project with.

Returns the full record of the newly created project.

Create a project

Creates a new section in a project.
Returns the full record of the newly created section.

Create a section in a project

Creates a new status update on an object.
Returns the full record of the newly created status update.

Create a status update

Adds a story to a task. This endpoint currently only allows for comment
stories to be created. The comment will be authored by the currently
authenticated user, and timestamped when the server receives the request.

Returns the full record for the new story added to the task.

Create a story on a task

Creates a new subtask and adds it to the parent task. Returns the full record for the newly created subtask.

Create a subtask

Creates a new tag in a workspace or organization.

Every tag is required to be created in a specific workspace or
organization, and this cannot be changed once set. Note that you can use
the workspace parameter regardless of whether or not it is an
organization.

Returns the full record of the newly created tag.

Create a tag in a workspace

Create a tag

Creating a new task is as easy as POSTing to the `/tasks` endpoint with a
data block containing the fields you’d like to set on the task. Any
unspecified fields will take on default values.

Every task is required to be created in a specific workspace, and this
workspace cannot be changed once set. The workspace need not be set
explicitly if you specify `projects` or a `parent` task instead.

Create a task

Creates a team within the current workspace.

Create a team

Creates a time tracking entry on a given task.

Returns the record of the newly created time tracking entry.

Create a time tracking entry

Establishing a webhook is a two-part process. First, a simple HTTP POST
request initiates the creation similar to creating any other resource.

Next, in the middle of this request comes the confirmation handshake.
When a webhook is created, we will send a test POST to the target with an
`X-Hook-Secret` header. The target must respond with a `200 OK` or `204
No Content` and a matching `X-Hook-Secret` header to confirm that this
webhook subscription is indeed expected. We strongly recommend storing
this secret to be used to verify future webhook event signatures.

The POST request to create the webhook will then return with the status
of the request. If you do not acknowledge the webhook’s confirmation
handshake it will fail to setup, and you will receive an error in
response to your attempt to create it. This means you need to be able to
receive and complete the webhook *while* the POST request is in-flight
(in other words, have a server that can handle requests asynchronously).

Invalid hostnames like localhost will recieve a 403 Forbidden status code.

```
# Request
curl -H "Authorization: Bearer <personal_access_token>" \
-X POST https://app.asana.com/api/1.0/webhooks \
-d "resource=8675309" \
-d "target=https://example.com/receive-webhook/7654"
```

```
# Handshake sent to https://example.com/
POST /receive-webhook/7654
X-Hook-Secret: b537207f20cbfa02357cf448134da559e8bd39d61597dcd5631b8012eae53e81
```

```
# Handshake response sent by example.com
HTTP/1.1 200
X-Hook-Secret: b537207f20cbfa02357cf448134da559e8bd39d61597dcd5631b8012eae53e81
```

```
# Response
HTTP/1.1 201
{
 "data": {
 "gid": "43214",
 "resource": {
 "gid": "8675309",
 "name": "Bugs"
 },
 "target": "https://example.com/receive-webhook/7654",
 "active": false,
 "last_success_at": null,
 "last_failure_at": null,
 "last_failure_content": null
 }
}
```

Establish a webhook

Deletes a specific, existing attachment.

Returns an empty data record.

Delete an attachment

A specific, existing custom field can be deleted by making a DELETE request on the URL for that custom field.
Locked custom fields can only be deleted by the user who locked the field.
Returns an empty data record.

Delete a custom field

A specific, existing goal can be deleted by making a DELETE request on the URL for that goal.

Returns an empty data record.

Delete a goal

A specific, existing membership can be deleted by making a `DELETE` request
on the URL for that membership.

Returns an empty data record.

Delete a membership

An existing portfolio can be deleted by making a DELETE request on
the URL for that portfolio.

Returns an empty data record.

Delete a portfolio

Deletes a specific, existing project brief.

Returns an empty data record.

Delete a project brief

*Deprecated: new integrations should prefer the `/status_updates/{status_gid}` route.*

Deletes a specific, existing project status update.

Returns an empty data record.

Delete a project status

A specific, existing project can be deleted by making a DELETE request on
the URL for that project.

Returns an empty data record.

Delete a project

A specific, existing section can be deleted by making a DELETE request on
the URL for that section.

Note that sections must be empty to be deleted.

The last remaining section cannot be deleted.

Returns an empty data block.

Delete a section

Deletes a specific, existing status update.

Returns an empty data record.

Delete a status update

Deletes a story. A user can only delete stories they have created.

Returns an empty data record.

Delete a story

A specific, existing tag can be deleted by making a DELETE request on
the URL for that tag.

Returns an empty data record.

Delete a tag

A specific, existing task can be deleted by making a DELETE request on
the URL for that task. Deleted tasks go into the “trash” of the user
making the delete request. Tasks can be recovered from the trash within a
period of 30 days; afterward they are completely removed from the system.

Returns an empty data record.

Delete a task

A specific, existing time tracking entry can be deleted by making a `DELETE` request on
the URL for that time tracking entry.

Returns an empty data record.

Delete a time tracking entry

This method *permanently* removes a webhook. Note that it may be possible to receive a request that was already in flight after deleting the webhook, but no further requests will be issued.

Delete a webhook

Creates and returns a job that will asynchronously handle the duplication.

Duplicate a project

Duplicate a task

Get the full record for a single attachment.

Get an attachment

Returns the compact records for all attachments on the object.

There are three possible `parent` values for this request: `project`, `project_brief`, and `task`. For a project, an attachment refers to a file uploaded to the "Key resources" section in the project Overview. For a project brief, an attachment refers to inline files in the project brief itself. For a task, an attachment refers to a file directly associated to that task.

Note that within the Asana app, inline images in the task description do not appear in the index of image thumbnails nor as stories in the task. However, requests made to `GET /attachments` for a task will return all of the images in the task, including inline images.

Get attachments from an object

Retrieve the audit log events that have been captured in your domain.

This endpoint will return a list of [AuditLogEvent](/reference/audit-log-api) objects, sorted by creation time in ascending order. Note that the Audit Log API captures events from October 8th, 2021 and later. Queries for events before this date will not return results.

There are a number of query parameters (below) that can be used to filter the set of [AuditLogEvent](/reference/audit-log-api) objects that are returned in the response. Any combination of query parameters is valid. When no filters are provided, all of the events that have been captured in your domain will match.

The list of events will always be [paginated](/docs/pagination). The default limit is 1000 events. The next set of events can be retrieved using the `offset` from the previous response. If there are no events that match the provided filters in your domain, the endpoint will return `null` for the `next_page` field. Querying again with the same filters may return new events if they were captured after the last request. Once a response includes a `next_page` with an `offset`, subsequent requests can be made with the latest `offset` to poll for new events that match the provided filters.

*Note: If the filters you provided match events in your domain and `next_page` is present in the response, we will continue to send `next_page` on subsequent requests even when there are no more events that match the filters. This was put in place so that you can implement an audit log stream that will return future events that match these filters. If you are not interested in future events that match the filters you have defined, you can rely on checking empty `data` response for the end of current events that match your filters.*

When no `offset` is provided, the response will begin with the oldest events that match the provided filters. It is important to note that [AuditLogEvent](/reference/audit-log-api) objects will be permanently deleted from our systems after 90 days. If you wish to keep a permanent record of these events, we recommend using a SIEM tool to ingest and store these logs.

Get audit log events

Returns a list of all of the custom fields settings on a portfolio, in compact form.

Get a portfolio's custom fields

Returns a list of all of the custom fields settings on a project, in compact form. Note that, as in all queries to collections which return compact representation, `opt_fields` can be used to include more data than is returned in the compact representation. See the [getting started guide on input/output options](https://developers.asana.com/docs/#input-output-options) for more information.

Get a project's custom fields

Get the complete definition of a custom field’s metadata.

Since custom fields can be defined for one of a number of types, and
these types have different data and behaviors, there are fields that are
relevant to a particular type. For instance, as noted above, enum_options
is only relevant for the enum type and defines the set of choices that
the enum could represent. The examples below show some of these
type-specific custom field definitions.

Get a custom field

Returns a list of the compact representation of all of the custom fields in a workspace.

Get a workspace's custom fields

Returns the compact representations of all of the dependencies of a task.

Get dependencies from a task

Returns the compact representations of all of the dependents of a task.

Get dependents from a task

Returns the full record for all events that have occurred since the sync
token was created.

A `GET` request to the endpoint `/[path_to_resource]/events` can be made in
lieu of including the resource ID in the data for the request.

Asana limits a single sync token to 100 events. If more than 100 events exist
for a given resource, `has_more: true` will be returned in the response, indicating
that there are more events to pull.

*Note: The resource returned will be the resource that triggered the
event. This may be different from the one that the events were requested
for. For example, a subscription to a project will contain events for
tasks contained within the project.*

Get events on a resource

Returns all of a user's favorites in the given workspace, of the given type.
Results are given in order (The same order as Asana's sidebar).

Get a user's favorites

Returns the complete updated goal relationship record for a single goal relationship.

Get a goal relationship

Returns compact goal relationship records.

Get goal relationships

Returns the complete goal record for a single goal.

Get a goal

Get goals

Get a list of the items in compact form in a portfolio.

Get portfolio items

Get a job by id

Returns compact `goal_membership`, `team_membership`, `project_membership`, `portfolio_membership`, or `workspace_membership` records. The possible types for `parent` in this request are `project`, `portfolio`, `team`, `goal`, and `workspace`. An additional member (user GID or team GID) can be passed in to filter to a specific membership. If a `parent` param is not provided, a `member`, `resource_subtype`, and `workspace` param must be provided.

Get multiple memberships

Returns details of a previously-requested Organization export.

Get details on an org export request

Returns a compact representation of all of the parent goals of a goal.

Get parent goals from a goal

Returns the complete portfolio record for a single portfolio membership.

Get a portfolio membership

Returns the compact portfolio membership records for the portfolio.

Get memberships from a portfolio

Returns a list of portfolio memberships in compact representation. You must specify `portfolio`, `portfolio` and `user`, or `workspace` and `user`.

Get multiple portfolio memberships

Returns the complete portfolio record for a single portfolio.

Get a portfolio

Returns a list of the portfolios in compact representation that are owned by the current API user.

Get multiple portfolios

Get a project brief

Returns the complete project record for a single project membership.

Get a project membership

Returns the compact project membership records for the project.

Get memberships from a project

*Deprecated: new integrations should prefer the `/status_updates/{status_gid}` route.*

Returns the complete record for a single status update.

Get a project status

*Deprecated: new integrations should prefer the `/status_updates` route.*

Returns the compact project status update records for all updates on the project.

Get statuses from a project

Returns the complete project template record for a single project template.

Get a project template

Returns the compact project template records for all project templates in the team.

Get a team's project templates

Returns the compact project template records for all project templates in the given team or workspace.

Get multiple project templates

Returns the complete project record for a single project.

Get a project

Returns a compact representation of all of the projects the task is in.

Get projects a task is in

Returns the compact project records for all projects in the team.

Get a team's projects

Returns the compact project records for all projects in the workspace.
*Note: This endpoint may timeout for large domains. Prefer the `/teams/{team_gid}/projects` endpoint.*

Get all projects in a workspace

Returns the compact project records for some filtered set of projects. Use one or more of the parameters provided to filter the projects returned.
*Note: This endpoint may timeout for large domains. Try filtering by team!*

White Label Loyalty + Asana integration

About Asana

Similar Integrations

Kustomer

Service Now

Teamwork CRM

Front

Benefits of White Label Loyalty + Asana

Integrate now!

Automate desired actions with Asana

Add a custom field to a portfolio

Add followers to a project

Add a custom field to a project

Set dependents for a task

Set dependencies for a task

Add followers to a task

Call and retrieve data from Asana

Wavin

Choose White Label Loyalty and become a loyalty leader

	list	find By Id	create	update	delete	search
Projects
Tags
Tasks
Teams
Users