Schedule a Playbook Run
Schedules a Playbook run.
Authorizations
Supply the API Key in the HTTP-Header
Headers
The Accept header specifies the media type that the client expects in the response. Available options: application/json, application/hal+json, application/xml, text/xml, text/csv. The default value is application/json.
application/json, application/hal+json, application/xml, text/xml, text/csv Path Parameters
The unique identifier for the Playbook.
24^[a-z0-9]{24}$Body
The unique identifier for the Snapshot or Project used for the Playbook run.
"61f25579055c2f43c249a181"
The Flow ID for the Playbook run.
"010d1970-89b9-4012-892b-53c78ef6c117"
The Locale ID for the Playbook run.
"8b3b45e2-48f9-446d-a4c5-35d8284a01b2"
Response
Playbook run successfully scheduled.
Created task metadata (same shape as ITaskReturnValue).
24^[a-z0-9]{24}$Task status (e.g. queued, active, done)
"queued"
Task type (e.g. runPlaybook)
"runPlaybook"
Task payload (playbookId, projectId, entrypoint, flowId, localeId, etc.)
Unix timestamp in seconds when the task was created
Unix timestamp in seconds when the task was last updated
Task progress (0-100)
0 <= x <= 100Present only when the task runs as a Kubernetes job