Trigger schedule now

POST/v1/schedules/{scheduleId}/trigger

Manually trigger a schedule and start a thread execution.

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
scheduleIdpathstringYesSchedule ID
Query parameters
None.

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 triggeredapplication/json
FieldTypeRequiredDescription
threadobjectNo—
executionobjectNo—
execution.idstringYesUnique identifier.
execution.scheduleIdstringYesSchedule ID.
execution.userIdstringYesUser ID.
execution.organizationIdstringNo—
execution.createdByUserIdstringNo—
execution.triggerTypeautomatic | manualYes—
execution.scheduledForstringYes—
execution.statusclaimed | running | completed | failedYesCurrent lifecycle status.
execution.threadIdstringNoThread ID.
execution.claimedBystringNo—
execution.leaseExpiresAtstringNo—
execution.startedAtstringNoISO 8601 timestamp.
execution.completedAtstringNoISO 8601 timestamp.
execution.errorstringNo—
execution.metadataobjectNoFree-form metadata object.
execution.createdAtstringYesISO 8601 timestamp.
execution.updatedAtstringYesISO 8601 timestamp.
execution.threadTitlestringNo—
execution.threadStatusstringNo—
execution.threadCreatedAtstringNo—
execution.threadCompletedAtstringNo—
execution.threadLastMessagePreviewstringNo—
execution.scheduleNamestringNo—
execution.appIdstringNo—
execution.contextIdstringNo—
messagestringNoMessage text.
Trigger schedule now
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow