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

{
  "jobExecutionId": "{JOB_EXECUTION_ID}",
  "status": "COMPLETED",
  "results": {
    "summary": "{SUMMARY}",
    "outputFiles": [
      "{OUTPUT_FILE_URL}"
    ],
    "data": {
      "{OUTPUT_KEY}": "{OUTPUT_VALUE}"
    }
  }
}
Once the status of a job is COMPLETED, you can use this endpoint to retrieve the results of the job execution.
This endpoint should only be called after the job status returns COMPLETED. Check the status first using Get Job Status.

​
Path Parameters

​
jobExecutionId
string
required
The ID of the job whose execution results you want to retrieve

​
Headers

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

​
Response

​
jobExecutionId
string
required
The job execution ID
​
status
string
required
The final status of the job (should be COMPLETED)
​
results
object
required
The workflow output data
The structure of the results object varies based on your workflow’s output schema definitions.
curl --request GET \
  --url https://operator.opus.com/job/{YOUR_JOB_EXECUTION_ID}/results \
  --header 'x-service-key: {YOUR_SERVICE_KEY}'

{
  "jobExecutionId": "{JOB_EXECUTION_ID}",
  "status": "COMPLETED",
  "results": {
    "summary": "{SUMMARY}",
    "outputFiles": [
      "{OUTPUT_FILE_URL}"
    ],
    "data": {
      "{OUTPUT_KEY}": "{OUTPUT_VALUE}"
    }
  }
}