One verification run with the outcome of each trace ID.
const url = 'https://example.com/api/v1/verifications/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/api/v1/verifications/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters”Responses
Section titled “ Responses ”The verification run.
object
Why a failed run failed.
The run’s own verdict, when the run is done. It is not the bundle’s Build Ready verdict.
The branch the SHA was the head of, when the target named a branch or a repo.
The commit the ranking compared against. Empty when the run had no base.
The content digest of a folder run.
object
Trace IDs outside the profile’s verify prefixes, which the gate did not verify.
The limits the scan hit.
The bundle got a new version after this run.
object
A test target is a citation, not a pass. Speccy runs no tests.
The outcome opened a blocking thread.
object
The file, relative to the repo root.
The verbatim anchor. It must appear in the file exactly once.
The line Speccy found the quote at.
Why the target does not hold.
Example
{ "status": "queued", "verdict": "verified", "outcomes": [ { "outcome": "implemented", "level": "MUST", "provenance": "claim", "targets": [ { "kind": "code", "provenance": "claim" } ] } ]}default
Section titled “default”An error.
RFC 9457 problem details with a stable code.
object
A stable machine-readable error code.
Examplegenerated
{ "type": "example", "title": "example", "status": 1, "detail": "example", "instance": "example", "code": "example"}