Path Parameters
The unique identifier of the parent workflow
The unique identifier of the execution
Headers
Your API key for authentication
Response Fields
The unique identifier of the execution
The ID of the parent workflow
The name of the workflow
The current status:
"completed", "failed", or "running"Key-value pairs of all workflow variables and their current values. Variable names are keys (e.g.,
variable_1, variable_2), values can be strings, booleans, arrays, or objects.The ID of the currently executing step (null if completed or failed)
The name of the current step (always null in current implementation)
URL to the video recording of the browser session (null if not available)
Whether public live view is enabled for this execution
ISO 8601 timestamp when the execution was created
ISO 8601 timestamp when the execution completed (null if still running or failed).
Error message if the execution failed (null if successful or running)
Array of log entries from the execution. May be empty (
[]) for executions without logged steps.Unique identifier for the log entry
The ID of the parent workflow execution
The ID of the step that generated this log
The attempt number for this step (steps may retry on failure)
Whether the step attempt succeeded
The log message, prefixed with step name in brackets (e.g., “[Browser Go to URL] Successful!”)
ISO 8601 timestamp when the log entry was created
Usage Notes
- API Key: Get your API key from the Dari dashboard
- Workspace Access: You can access executions in your workflow’s workspace, including those created by other workspace members
- Variables: Output variables are populated as steps complete. Variable names follow the pattern
variable_1,variable_2, etc. Values can be strings, booleans, arrays, or objects. - Logs: Logs array may be empty (
[]) for some executions. When present, logs are ordered chronologically and include both successful and failed step attempts. - Polling: For running executions, poll this endpoint periodically to check status updates