List project schedules

GET/v1/projects/{projectId}/schedules

List schedules attached to a project across its tickets, threads, and automations.

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
NameLocationTypeRequiredDescription
rangeStartquerystringNoOptional lower bound for schedule occurrence filtering.
rangeEndquerystringNoOptional upper bound for schedule occurrence filtering.

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.

200Project schedule listapplication/json
FieldTypeRequiredDescription
objectstringNo
dataobject[]No
data[].idstringNoUnique identifier.
data[].userIdstringNoUser ID.
data[].namestringNoHuman-readable name.
data[].descriptionstringNoHuman-readable description.
data[].agentIdstringNoAgent ID.
data[].agentNamestringNo
data[].taskstringNo
data[].environmentIdstringNoComputer ID.
data[].environmentNamestringNo
data[].appIdstringNo
data[].contextIdstringNo
data[].contextNamestringNo
data[].scheduleTypeone-time | recurringNo
data[].cronExpressionstringNo
data[].scheduledTimestringNo
data[].timezonestringNo
data[].enabledbooleanNo
data[].lastRunAtstringNo
data[].nextRunAtstringNo
data[].runCountintegerNo
data[].successCountintegerNo
data[].failureCountintegerNo
data[].metadataobjectNoFree-form metadata object.
data[].createdAtstringNoISO 8601 timestamp.
data[].updatedAtstringNoISO 8601 timestamp.
has_morebooleanNo
total_countintegerNo
404Resource not foundapplication/json
FieldTypeRequiredDescription
errorstringNo
List project schedules
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow