Create sprint

POST/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
None.

Body schema

Content type: application/json · Required

FieldTypeRequiredDescription
projectIdstringNoProject ID.
namestringYesHuman-readable name.
goalstringNo
statusplanned | active | completedNoCurrent lifecycle status.
startAtstringNo
endAtstringNo
sortOrdernumberNo
metadataobjectNoFree-form metadata object.

What the API returns

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

201Sprint createdapplication/json
FieldTypeRequiredDescription
sprintobjectNo
sprint.idstringNoUnique identifier.
sprint.userIdstringNoUser ID.
sprint.projectIdstringNoProject ID.
sprint.namestringNoHuman-readable name.
sprint.goalstringNo
sprint.statusplanned | active | completedNoCurrent lifecycle status.
sprint.startAtstringNo
sprint.endAtstringNo
sprint.sortOrdernumberNo
sprint.metadataobjectNoFree-form metadata object.
sprint.createdAtstringNoISO 8601 timestamp.
sprint.updatedAtstringNoISO 8601 timestamp.
Create sprint
Loading...
Response 201
Loading...
See the ACP quickstart and SDK flow