Skip to main content
GET
What this scan was gated by

Authorizations

Authorization
string
header
required

An Earnie API key, sent as Authorization: Bearer sk_earnie_.... Create one under Settings > API keys. The key's scopes decide which operations it may call.

Path Parameters

scanId
string<uuid>
required

Response

The revisions this scan evaluated, its per-policy verdicts and their evidence

Everything one scan was gated by, anchored to that scan: the revisions it evaluated, the per-policy verdicts, and the per-finding evidence those evaluations produced, with the current Policy Approval overlay applied on top.

It deliberately carries no gate. This read sees only what was recorded, and a gate is a statement about a scan's whole run: a scan that has not reached policy evaluation and a scan no policy applied to leave the same absence here, and one that failed AFTER evaluation leaves a full set of verdicts whose collapse would read green. Only GET /v1/scans/{scanId} knows the scan's own lifecycle, so it owns gate, gate_reason and evaluation. Read the gate there and read this route to learn which policies produced it.

scan_id
string<uuid>
required
policies
object[]
required

One entry per policy the scan was linked to an evaluation for, by ascending policy_id. Empty when nothing was recorded — which is not the same as "no policy applied"; see the schema description.

verdicts
object[]
required

The per-finding verdicts of those same evaluations, with their stored evidence and the live approval overlay. This is the population the evaluation ran over, which for a partial scan is wider than the findings that scan itself touched — the gate was collapsed from all of it.

evaluated_at
string<date-time> | null

When the scan-anchored evaluation ran — the earliest started_at among the evaluations this scan is linked to. Null when none is recorded for it.

gate_updated_at
string<date-time> | null

When an approval overlaying these verdicts last moved it — granted, revoked, or lapsed. Null when none ever has.

Not quite "when the gate changed": an approval that covers one of two violations moves the overlay without moving the gate, and it is stamped here either way. scan.gate_updated in the Audit Log is the record of the gate actually changing, and is emitted only when it did — including for a lapse, which nothing notices, so a gate that re-blocked on expiry shows the moment here without a matching event on the trail.