Background runs let you submit an agent task and receive an immediate acknowledgement, then poll for the result at your own pace. This is the right choice for long-running analyses, batch processing, and workflow steps where you cannot hold an HTTP connection open for the full duration of execution. All requests require a valid bearer token in theDocumentation Index
Fetch the complete documentation index at: https://operativusai.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Authorization header.
Submit a background run
runId and status: "QUEUED". The request accepts the same body as the synchronous run endpoint.
Path parameters
The unique identifier of the agent to run.
Request body
The user’s input or query for the agent.
UUID of an existing session to continue. Omit to start a new session — the server generates one automatically.
Associates the run with a specific user for memory scoping and audit trails.
Tenant identifier for multi-tenant deployments.
When
true, the agent generates suggested follow-up questions appended to the output.Array of multimodal inputs. Each entry contains
type (MIME type) and data (base64 or URL).Optional model overrides (
model, temperature, maxTokens).Response
Unique identifier for the queued run. Use this to poll for status.
Always
"QUEUED" on successful submission.Poll for run status
AgentRun entity. Poll this endpoint until status reaches a terminal state (COMPLETED, FAILED, or CANCELLED).
The agent that owns the run.
The run identifier returned when the background run was submitted.
| Status | Description |
|---|---|
QUEUED | The run has been accepted and is waiting in the job queue. |
RUNNING | The agent is actively processing the request. |
COMPLETED | Execution finished successfully. Check output for the response. |
FAILED | An unrecoverable error occurred. |
PAUSED | The agent triggered a Human-in-the-Loop gate. Call /runs/{runId}/continue to approve or reject. |
CANCELLED | The run was cancelled via DELETE /api/agents/{agentId}/runs/{runId}. |
The run ID.
The agent that executed this run.
The session this run belongs to.
Current execution status.
ISO-8601 timestamp when the run was queued.
ISO-8601 timestamp when the run reached a terminal status.
null while still running.The agent’s response content, available when
status is "COMPLETED".Batch status polling
The agent that owns the runs.
Comma-separated list of run IDs to check. Maximum 100 IDs per request.
Polling loop example
The following TypeScript example submits a background run and polls for completion with exponential backoff:For batch workloads, use the batch status endpoint (
?runIds=...) instead of individual polling calls. Checking 10 runs at once with one request every 3 seconds uses ~20 requests/minute compared to ~200 for individual polls.