PUT /memberships/{membership_gid}
An existing membership can be updated by making a PUT request on the membership. Only the fields provided in the data block will be updated;
any unspecified fields will remain unchanged. Memberships on goals, projects, portfolios, custom_types, and custom_fields can be updated.
Returns the full record of the updated membership.
Servers
- https://app.asana.com/api/1.0
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
membership_gid |
String | Yes |
Globally unique identifier for the membership. |
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
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. |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
data |
Object | No | |
data.access_level |
String | No |
Sets the access level for the member. Goals can have access levels |
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.