API · Automations

Retrieve Automation Run

Retrieve an automation run and its step history in workflow order (requires full access).

GET/automations/{automation_id}/runs/{run_id}Full access

Request parameters

Parameter	Type	Description
`automation_id` path · required	`string`	The ID of the automation.
`run_id` path · required	`string`	The ID of the automation run.

Request example

Set OPENSEND_BASE_URL=https://api.example.com and OPENSEND_API_KEY=os_replace_me on your server.

bash

curl -X GET "$OPENSEND_BASE_URL/automations/YOUR_automation_id/runs/YOUR_run_id" \
  -H "Authorization: Bearer $OPENSEND_API_KEY"

Response

200 · application/json. Example IDs stand for IDs returned by your installation.

json

{
  "object": "automation_run",
  "id": "YOUR_ID",
  "status": "running",
  "started_at": "2023-10-06 23:47:56.678+00",
  "completed_at": "2023-10-06 23:47:56.678+00",
  "created_at": "2023-10-06 23:47:56.678+00",
  "steps": [
    {
      "key": "example",
      "type": "trigger",
      "status": "example",
      "started_at": "2023-10-06 23:47:56.678+00",
      "completed_at": "2023-10-06 23:47:56.678+00",
      "output": "example",
      "error": "example",
      "created_at": "2023-10-06 23:47:56.678+00"
    }
  ]
}

Behavior and errors

The run must belong to the automation in the URL. Steps follow graph order. Output, error, and completion timestamps can be null.

Use a full-access credential. Unknown or foreign resources return 404. See authentication, errors, rate limits, and pagination.