Search + K

Command Palette

Search for a command to run...

Sign In

Update a goal relationship

PUT /goal_relationships/{goal_relationship_gid}
Copy endpoint
https://app.asana.com/api/1.0

An existing goal relationship can be updated by making a PUT request on the URL for that goal relationship. Only the fields provided in the data block will be updated; any unspecified fields will remain unchanged.

Returns the complete updated goal relationship record.

Parameters

path Path Parameters

Name Type
goal_relationship_gid required

Globally unique identifier for the goal relationship.

string

query Query Parameters

Name Type
opt_fields

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.

("contribution_weight" | "resource_subtype" | "supported_goal" | "supported_goal.name" | "supported_goal.owner" | "supported_goal.owner.name" | "supporting_resource" | "supporting_resource.name")[]
opt_pretty

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.

boolean

Request Body

application/json required

The updated fields for the goal relationship.

{ data?: GoalRelationshipRequest
type GoalRelationshipRequest = GoalRelationshipBase & {}
; }

Responses

200 application/json

Successfully updated the goal relationship.

{ data?: GoalRelationshipResponse
type GoalRelationshipResponse = GoalRelationshipBase & {}
; }

Client Errors

400 application/json

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

interface ErrorResponse {
errors?: Error
interface Error {
message?: string;
help?: string;
phrase?: string;
}
[]
;
}
401 application/json

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

interface ErrorResponse {
errors?: Error
interface Error {
message?: string;
help?: string;
phrase?: string;
}
[]
;
}
403 application/json

The 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.

interface ErrorResponse {
errors?: Error
interface Error {
message?: string;
help?: string;
phrase?: string;
}
[]
;
}
404 application/json

Either 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.

interface ErrorResponse {
errors?: Error
interface Error {
message?: string;
help?: string;
phrase?: string;
}
[]
;
}

Server Errors

500 application/json

There 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.

interface ErrorResponse {
errors?: Error
interface Error {
message?: string;
help?: string;
phrase?: string;
}
[]
;
}