Skip to main content
GET
/
job
/
{jobExecutionId}
/
audit
curl --request GET \
  --url https://operator.opus.com/job/{YOUR_JOB_EXECUTION_ID}/audit \
  --header 'x-service-key: {YOUR_SERVICE_KEY}'

{
  "nb_nodes": 5,
  "executed_nodes": ["{NODE_ID_1}", "{NODE_ID_2}"],
  "nb_executed_nodes": 2,
  "running_node": "{NODE_ID_3}",
  "next_node_to_execute": "{NODE_ID_4}",
  "remaining_nodes_to_execute": ["{NODE_ID_4}", "{NODE_ID_5}"],
  "failed_nodes": [],
  "nb_failed_nodes": 0,
  "audit": {
    "nodes_execution_data": {
      "{NODE_ID_1}": {
        "{KEY}": "{VALUE}"
      },
      "{NODE_ID_2}": {
        "{KEY}": "{VALUE}"
      }
    }
  }
}
Opus exposes a node-level audit for every job. The response shows you which nodes have run, which is running now, which are still queued, and which have failed — together with the per-node execution data that the workflow engine produced. Use it for debugging, compliance, or building progress visualisations on top of a running job.

​
Path Parameters

​
jobExecutionId
string
required
The ID of the job whose audit log you want to retrieve

​
Headers

​
x-service-key
string
required
Your API authentication key

​
Response

​
nb_nodes
number
required
Total number of nodes in the workflow.
​
executed_nodes
string[]
required
IDs of nodes that have already finished executing, in the order they ran.
​
nb_executed_nodes
number
required
Number of nodes that have finished executing. Equal to executed_nodes.length.
​
running_node
string
required
ID of the node currently executing. Empty string when no node is actively running (for example, between nodes or after the job finishes).
​
next_node_to_execute
string
required
ID of the node scheduled to run next. Empty string when the job has no more nodes queued.
​
remaining_nodes_to_execute
string[]
required
IDs of nodes that are still pending execution.
​
failed_nodes
string[]
required
IDs of nodes that failed during execution.
​
nb_failed_nodes
number
required
Number of failed nodes. Equal to failed_nodes.length.
​
audit
object
required
Per-node execution data captured by the engine.
curl --request GET \
  --url https://operator.opus.com/job/{YOUR_JOB_EXECUTION_ID}/audit \
  --header 'x-service-key: {YOUR_SERVICE_KEY}'

{
  "nb_nodes": 5,
  "executed_nodes": ["{NODE_ID_1}", "{NODE_ID_2}"],
  "nb_executed_nodes": 2,
  "running_node": "{NODE_ID_3}",
  "next_node_to_execute": "{NODE_ID_4}",
  "remaining_nodes_to_execute": ["{NODE_ID_4}", "{NODE_ID_5}"],
  "failed_nodes": [],
  "nb_failed_nodes": 0,
  "audit": {
    "nodes_execution_data": {
      "{NODE_ID_1}": {
        "{KEY}": "{VALUE}"
      },
      "{NODE_ID_2}": {
        "{KEY}": "{VALUE}"
      }
    }
  }
}