POST /v1/jobs/:id/cancel cancels a parent job’s remaining non-terminal children. Children that already reached a terminal state (completed, partial, failed) keep their outcome and their artifacts — cancellation only stops work that hasn’t finished.
id
string
required
The parent job id (dotless, e.g. job_8t2q).

Request

Response

200 OK
job.id
string
The parent job id.
job.status
string
The parent’s status after cancellation. If some children had already completed, the rollup can be partial or completed rather than canceled — cancellation never rewrites a finished child’s result.
Cancellation is a request to stop, not a rollback. A capture already in flight may still finish; a successful capture is still billed. Only work that hadn’t started is guaranteed not to run (or be charged).

Errors

404
JOB_NOT_FOUND
No parent job exists for that id, or it belongs to another tenant (reads and writes are owner-scoped — another tenant’s id is a 404, never a 403).
404

Get a job

Read the parent rollup and per-child status.

Job lifecycle

Terminal states and when work can still be canceled.