Checks_GetCheck
const url = 'https://junction-api.qualiastudios.dev/v1/accounts/example/checks/example';const options = {method: 'GET', headers: {'X-API-Key': '<X-API-Key>'}};
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://junction-api.qualiastudios.dev/v1/accounts/example/checks/example \ --header 'X-API-Key: <X-API-Key>'Gets one check.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The account id.
The check id.
Responses
Section titled “ Responses ”OK
A check the server runs over a dataset. Every account has the same four;
the {check} id is the kind as a lowercase slug: episode-rules,
mixture, reach, vlm. Everything a check needs (its results
and reference ranges) lives under it.
Served by qds-api.
object
Accounts/{account}/checks/{check}
Which check it is.
One sentence: what it checks.
The dataset kinds it runs on.
Whether the check stores a CheckResult per episode. Only reach does.
A check’s computed values are its source and its issues are alerts
derived from them: reach’s source is its results; the episode rules’
is Episode.metrics and their reference ranges; so their results
collection is empty. The VLM check’s readings are kept with its
issues, which are what it reports: each issue it raised carries its
reading (Issue.finding).
Whether this deployment can run it. False only for vlm where the
deployment has no VLM check pipeline template or no source of published
tasks: RunCheck on it is then FAILED_PRECONDITION. A client offers a run
only where it is true.
Example
{ "kind": "KIND_UNSPECIFIED", "datasetKinds": [ "KIND_UNSPECIFIED" ]}default
Section titled “default ”Default error response
A refusal from the API itself.
object
The gRPC code name in upper case, e.g. NOT_FOUND.
Whether the same call may succeed if retried.
Empty, except when a dataset copy or move is refused: then one google.rpc.ErrorInfo with the refusal’s reason code, its domain and, in metadata, the datasets it names.
object
A refusal from the gateway before the call reaches the API, for example 401 bad or missing API key, 403 key lacks the scope or environment closed, 413 body too large.
object
What went wrong.
Example generated
{ "code": "example", "message": "example", "retryable": true, "details": [ {} ]}