Jobs
AuthorizationBearer <token>Project API key (dtn_…) as a Bearer token. Mint via the management API (POST /projects/:id/api-keys) or this deployment's key-mint CLI. Every key carries an explicit set of verb:resource project permissions chosen at mint time (PLAN-API-KEY-PERMISSIONS.md); each operation lists the project permission it requires in its security requirement, and a key lacking it is answered 403 missing required project permission: <project-permission>. Some operations require an additional permission depending on the request body, stated in the operation's description. Holding a mutating verb (write:/delete:/invoke:) implies the resource's read: permission. Operations whose api_key project-permission list is empty need no specific project permission — any live project key works (the global catalogs and the artifact-cache read).
Scope: read:sandboxes
id*stringjob id
uuidJob status
application/json- response
One async job's status.
attempts*integerDelivery attempts so far.
int32error?|Failure detail, if the job errored.
id*stringuuidkind*stringJob kind (e.g. vm.create, build, snapshot.create).
runner_id?|Runner the job was dispatched to, once assigned.
status*stringLifecycle status: queued, running, done, or failed.
curl -X GET 'https://example.com/jobs/497f6eca-6276-4993-bfeb-53cbbbba6f08'{ "attempts": 0, "error": "string", "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "kind": "string", "runner_id": "string", "status": "string"}