Create project work relation

POST/v1/projects/{projectId}/work-relations

Creates a normalized task relation. Blocks relations are mirrored into the target task dependency list and rejected when they would create a cycle.

How to call this endpoint

Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.

Path, query, and header parameters

These parameters control which ACP object the endpoint acts on and how the request is processed.

Path parameters
NameLocationTypeRequiredDescription
projectIdpathstringYesProject ID
Query parameters
None.

Body schema

Content type: application/json · Required

FieldTypeRequiredDescription
sourceTaskIdstringYes
targetTaskIdstringYes
relationTypeblocks | parent_of | duplicates | relates_toYes
metadataobjectNoFree-form metadata object.

What the API returns

Each response code below includes the documented payload shape for the ACP API.

201Project work relation createdapplication/json
FieldTypeRequiredDescription
relationobjectNo
relation.idstringYesUnique identifier.
relation.userIdstringYesUser ID.
relation.organizationIdstringNo
relation.createdByUserIdstringNo
relation.projectIdstringYesProject ID.
relation.sourceTaskIdstringYes
relation.targetTaskIdstringYes
relation.relationTypeblocks | parent_of | duplicates | relates_toYes
relation.metadataobjectNoFree-form metadata object.
relation.createdAtstringYesISO 8601 timestamp.
relation.updatedAtstringYesISO 8601 timestamp.
400Response
None.
404Resource not foundapplication/json
FieldTypeRequiredDescription
errorstringNo
409Relation would create a dependency cycle
None.
Create project work relation
Loading...
Response 201
Loading...
See the ACP quickstart and SDK flow