Executions endpoint

Retrieve Execution

GET/execution-runs/{runId}/

Path parameters

runId

Identifier used by the registered route.

Request body

none

This endpoint does not accept a request body.

Query parameters

view

Read model to return. Execution views include monitor, status, activity, logs, events, and data; catalog endpoints also expose options, summary, inventory, or count views.

cURL template

curl --fail-with-body \
  -H "Authorization: Bearer ${AKOFLOW_API_TOKEN}" \
  "${AKOFLOW_API_URL}/execution-runs/{runId}/"

Replace the path identifiers with IDs from your instance.

200 OKapplication/json

Handler-checked response shape; values and optional fields vary.

{
  "run": {
    "id": "run-id",
    "schedulePlanId": "plan-id",
    "mode": "simulation",
    "seed": 0,
    "status": "completed",
    "makespanSeconds": 12.4,
    "cost": 0,
    "breakdown": {
      "computeSeconds": 12.4,
      "transferSeconds": 0,
      "queueSeconds": 0,
      "interferenceSeconds": 0,
      "overheadSeconds": 0
    },
    "transferredBytes": 0,
    "kind": "workflow"
  },
  "activities": [],
  "dataTransfers": [],
  "handles": [],
  "events": []
}

Response shape

The response always has run, activities, dataTransfers, handles, and events. With cloud operations configured, it also has infrastructureRuns. With the data catalog configured, it also has dataObjects, dataLocations, artifactMaterializations, and artifactTransferRuns. The example shows the core fields of a completed workflow run; optional run fields and related arrays vary by run and server configuration.

Related guide

See the Executions guide for related tasks and context.