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

{
  "jobResultsPayloadSchema": {
    "{OUTPUT_VARIABLE_1}": {
      "value": "{STRING_VALUE}",
      "type": "str",
      "displayName": "Summary"
    },
    "{OUTPUT_VARIABLE_2}": {
      "value": "{FILE_URL}",
      "type": "file",
      "displayName": "Generated Report"
    }
  }
}
Once the status of a job is COMPLETED, you can use this endpoint to retrieve the results of the job execution. The response contains a single top-level field, jobResultsPayloadSchema, whose keys are the output variable names defined by your workflow.
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. This is the jobExecutionId returned from Initiate Job.

​
Headers

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

​
Response

​
jobResultsPayloadSchema
object
required
The workflow’s output payload, keyed by output variable name. Each entry is a Variable Object whose shape mirrors the inputs you provided in Execute Job.
The keys inside jobResultsPayloadSchema are defined by your workflow’s output schema and will vary between workflows. The example below is illustrative — your output variable names will differ.
curl --request GET \
  --url https://operator.opus.com/job/{YOUR_JOB_EXECUTION_ID}/results \
  --header 'x-service-key: {YOUR_SERVICE_KEY}'

{
  "jobResultsPayloadSchema": {
    "{OUTPUT_VARIABLE_1}": {
      "value": "{STRING_VALUE}",
      "type": "str",
      "displayName": "Summary"
    },
    "{OUTPUT_VARIABLE_2}": {
      "value": "{FILE_URL}",
      "type": "file",
      "displayName": "Generated Report"
    }
  }
}