List releases

GET/v1/tasks/releases

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
None.
Query parameters
NameLocationTypeRequiredDescription
projectIdquerystringNo
qquerystringNo
limitqueryintegerNo
offsetqueryintegerNo

Body schema

This endpoint does not require a request body.

None.

What the API returns

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

200Release listapplication/json
FieldTypeRequiredDescription
objectstringNo
dataobject[]No
data[].objectstringNo
data[].idstringNoUnique identifier.
data[].userIdstringNoUser ID.
data[].projectIdstringNoProject ID.
data[].namestringNoHuman-readable name.
data[].descriptionstringNoHuman-readable description.
data[].startAtstringNo
data[].endAtstringNo
data[].sortOrdernumberNo
data[].statusplanned | active | completedNoCurrent lifecycle status.
data[].metadataobjectNoFree-form metadata object.
data[].taskCountintegerNo
data[].openTaskCountintegerNo
data[].taskIdsstring[]No
data[].createdAtstringNoISO 8601 timestamp.
data[].updatedAtstringNoISO 8601 timestamp.
has_morebooleanNo
total_countintegerNo
List releases
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow