List schedule executions

GET/v1/schedules/executions

List durable execution lifecycle records for Calendar and automation schedules in the active organization.

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
scheduleIdquerystringNo
appIdquerystringNo
contextIdquerystringNo
rangeStartquerystringNo
rangeEndquerystringNo
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.

200Schedule execution listapplication/json
FieldTypeRequiredDescription
objectstringYes
dataobject[]Yes
data[].idstringYesUnique identifier.
data[].scheduleIdstringYesSchedule ID.
data[].userIdstringYesUser ID.
data[].organizationIdstringNo
data[].createdByUserIdstringNo
data[].triggerTypeautomatic | manualYes
data[].scheduledForstringYes
data[].statusclaimed | running | completed | failedYesCurrent lifecycle status.
data[].threadIdstringNoThread ID.
data[].claimedBystringNo
data[].leaseExpiresAtstringNo
data[].startedAtstringNoISO 8601 timestamp.
data[].completedAtstringNoISO 8601 timestamp.
data[].errorstringNo
data[].metadataobjectNoFree-form metadata object.
data[].createdAtstringYesISO 8601 timestamp.
data[].updatedAtstringYesISO 8601 timestamp.
data[].threadTitlestringNo
data[].threadStatusstringNo
data[].threadCreatedAtstringNo
data[].threadCompletedAtstringNo
data[].threadLastMessagePreviewstringNo
data[].scheduleNamestringNo
data[].appIdstringNo
data[].contextIdstringNo
has_morebooleanYes
List schedule executions
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow