Jobs
Execute Job
Run a workflow with populated inputs
POST
This is the primary step where you provide all inputs and run the workflow.
The request body consists of:
- The
jobExecutionIdfrom the Initiate Job step - The
jobPayloadSchemaInstance— the schema from Get Workflow Details with values populated for each input - A
callbackUrlthat Opus will POST to when the job finishes
Job execution is asynchronous. This endpoint returns immediately once the run is queued; the final result is delivered to your
callbackUrl (and is also retrievable via Get Job Results).Headers
string
required
Your API authentication key
Body Parameters
string
required
The ID of the job to execute (received from Initiate Job)
object
required
An object where each key is a variable name from your workflow schema, and each value is a Variable Object (see below).
string
required
HTTPS URL that Opus will POST the job result to once the run finishes. Must be reachable from the Opus platform.
string
Optional comma-separated workspace IDs used to validate workflow access. Used by machine-key callers that operate across multiple workspaces.
Variable Object
Each entry injobPayloadSchemaInstance uses your variable name as the key (e.g., VARIABLE_NAME_1) and maps to an object with the following properties:
any
required
The value for this input (type depends on field type)
string
required
The data type: str, float, bool, date, file, array, array_files, or object
string
The variable name displayed in the Opus platform UI
Response
boolean
required
Whether the job execution was successfully started
string
required
The job execution ID
string
required
Status message