Jobs
Initiate Job
Create a new job instance and receive a jobExecutionId
POST
This step creates a job instance in the system and returns the unique
jobExecutionId required for execution and monitoring.
You can identify the workflow with either workflowId or referenceEntityId (a workflow reference entity UUID). If both are sent, referenceEntityId takes precedence. The job runs against the latest active version of the workflow unless you pin one with workflowVersionId or workflowVersionNumber.
Headers
string
required
Your API authentication key
Body Parameters
string
The ID of the workflow to be used for your job. Required unless
referenceEntityId is provided. The platform resolves it to a workflow reference entity via lookup.string
Workflow reference entity UUID. Required unless
workflowId is provided. Takes precedence over workflowId if both are sent.string
Pin the job to a specific workflow version by UUID. Omit to run the latest active version.
number
Pin the job to a specific workflow version by version number. Omit to run the latest active version.
string
Job title shown in the Opus UI
string
Job description shown in the Opus UI
string
The ID of the user who initiated the job. Useful for attributing API-triggered jobs back to a specific end user.
string
default:"api"
Where the job was triggered from. Defaults to
api for service-key callers. Allowed values: email-agent, chat-agent, scheduled, api, manual, agent, opus-ai, web-app.string
Optional comma-separated workspace IDs used to validate workflow access. Used by machine-key callers that operate across multiple workspaces.
object
Initial user-provided inputs to store on the job at creation time. Accepts arbitrary key/value pairs that match your workflow’s input schema.
string
The ID of the web app that initiated this job, when the job is launched from a published Opus web app.
Response
string
required
The unique identifier for this job execution. Use this ID in all subsequent API calls.