Cancel a background job
Stop a job and the run it drives.
cancelled, and its run is stopped too. Rows the run already found are kept. Cancelling a batch stops every job in it that is still open.
The answer is the job as it is now: while it stops, status is still queued or running with cancel_requested: true. A job that already ended is left as it is, and status says how it ended.
Only your own; anyone else gets 404. Needs jobs:write. MCP tool: cancel_job.Authorizations
API key with the vd_sk_ prefix, as Authorization: Bearer vd_sk_.... Create keys in Settings → API Keys.
Headers
Any unique string (such as your order id). Resending the same request with the same key within 24 hours returns the first answer (with Idempotent-Replayed: true) and does nothing twice; the same key with a different request is a 422 idempotency_key_reused.
1 - 255Path Parameters
Response
The job as it is now: stopping, or left as it was because it had already ended.
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.

