Skip to main content
GET
Get an execution

Authorizations

X-API-Key
string
header
required

Path Parameters

execution_id
string
required

Response

Successful Response

id
string
required
batch_id
string
required
trigger_id
string
required
trigger_type
string
required
definition_id
string
required
org_id
string
required
status
enum<string>
required
Available options:
pending,
running,
waiting,
completed,
failed,
cancelled
input_data
Input Data · object
required
workflow_id
string | null
required
started_at
string<date-time> | null
required
completed_at
string<date-time> | null
required
result
Result · object | null
required
error
string | null
required
created_at
string<date-time>
required
updated_at
string<date-time>
required
job_id
string
default:""
trigger_source
string | null
steps
StepDetail · object[] | null
steps_source
enum<string> | null

Indicates where the steps array on an execution detail comes from.

Always present on GET /executions/{id} so a client can distinguish a run that genuinely has no steps from one whose step detail is unavailable.

Available options:
live,
snapshot,
unavailable
quiet_hours_hold
QuietHoursHold · object | null

Why a run's next message is waiting, when it is waiting for the clock.

Text messages may only be sent during daytime hours in the recipient's own local time. A message outside that window is held and sent when the window opens, and this object is how a run says so: it is present on GET /executions/{id} only while such a hold is in force, and its presence is what distinguishes waiting for a legal hour from waiting for a person.