Get a background job
One job: its status, and once it ended, what came back.
status is completed, failed, or cancelled. Then summary is one plain line of what came back, result has the row count and a preview of the first rows, and error says why it failed. cancel_requested is true while a job is being stopped.
run_ref is the run the job drives: read every row with Get a run. link is the page in Valendata that shows it. A batch job has no run of its own; the jobs in it have its id as their group_id.
Only your own; anyone else gets 404. Needs jobs:read. MCP tool: get_job.Authorizations
API key with the vd_sk_ prefix, as Authorization: Bearer vd_sk_.... Create keys in Settings → API Keys.
Path Parameters
Response
The job: once it ended, its summary and result.
Who started it: session (a chat session's agent), igris (the assistant), brain (a workflow's Brain, which may report results) or api.
session, igris, brain, api What it runs: a skill, a workflow, a research helper, or a batch grouping jobs started together.
skill, workflow, research, batch queued, running, then one of completed, failed, cancelled.
queued, running, completed, failed, cancelled The session or workflow that started it; empty for the assistant and the API.
The batch job it belongs to, when several were started together.
What it is, in the words it was started with, e.g. 'eBay search'.
The skill or workflow it runs.
The run it drives (GET /v1/runs/{run_id} for a skill or workflow); null until it has started.
One plain line of what came back, once it ended.
A small result: count and a preview of the first rows. The run has the rest.
Why it failed.
A stop was asked for; it ends cancelled soon.
How many times its run was started.
The path of the page in the Valendata app that shows its run (e.g. /skills/runs/run_…); empty until it has started.

