コンテンツにスキップ

One analysis job by id.

GET
/api/v1/analysis/jobs/{id}
curl --request GET \
--url https://example.com/api/v1/analysis/jobs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0 \
--header 'Authorization: Bearer <token>'
id
required
string format: uuid

Analysis job id

The job row, including its state and progress

Media typeapplication/json

A job row, as served to the API / SSE. Timestamps are epoch-millis so the WebUI formats relative times without a date dependency.

object
created_ms
required
integer format: int64
error
string | null
finding_count
required
integer format: int32
finished_ms
integer | null format: int64
id
required
string format: uuid
params
required
pct
required
integer format: int32
phase
string | null
scope_id
string | null format: uuid
scope_kind
required
string
scope_label
required
string
started_ms
integer | null format: int64
state
required
string
summary
string | null
tool
required
string
Examplegenerated
{
"created_ms": 1,
"error": "example",
"finding_count": 1,
"finished_ms": 1,
"id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0",
"params": "example",
"pct": 1,
"phase": "example",
"scope_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0",
"scope_kind": "example",
"scope_label": "example",
"started_ms": 1,
"state": "example",
"summary": "example",
"tool": "example"
}

No valid bearer token

Media typeapplication/json

The ADR-019 envelope every failure renders as. pub(crate) and schema-bearing so the OpenAPI document can name one error shape for every endpoint (ADR-035) instead of leaving 4xx/5xx bodies undescribed — a client that has to guess the failure shape ends up parsing the success shape and reading undefined.

object
error
required
object
code
required

Stable machine-readable code. Clients branch on this, never on the message.

string
message
required

Operator-facing sentence. Safe to display; never carries an internal error’s own text.

string
Examplegenerated
{
"error": {
"code": "example",
"message": "example"
}
}

Role lacks the read permission

Media typeapplication/json

The ADR-019 envelope every failure renders as. pub(crate) and schema-bearing so the OpenAPI document can name one error shape for every endpoint (ADR-035) instead of leaving 4xx/5xx bodies undescribed — a client that has to guess the failure shape ends up parsing the success shape and reading undefined.

object
error
required
object
code
required

Stable machine-readable code. Clients branch on this, never on the message.

string
message
required

Operator-facing sentence. Safe to display; never carries an internal error’s own text.

string
Examplegenerated
{
"error": {
"code": "example",
"message": "example"
}
}

No such job — also the answer when this deployment has no runner

Media typeapplication/json

The ADR-019 envelope every failure renders as. pub(crate) and schema-bearing so the OpenAPI document can name one error shape for every endpoint (ADR-035) instead of leaving 4xx/5xx bodies undescribed — a client that has to guess the failure shape ends up parsing the success shape and reading undefined.

object
error
required
object
code
required

Stable machine-readable code. Clients branch on this, never on the message.

string
message
required

Operator-facing sentence. Safe to display; never carries an internal error’s own text.

string
Examplegenerated
{
"error": {
"code": "example",
"message": "example"
}
}