List sprints

GET/v1/tasks/sprints

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
projectIdquerystringNoFilter to a specific project. Use `none` for unscoped sprints.
statusqueryplanned | active | completedNo
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.

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