/v1/displays/{id}/lintLint a stored display document
operation ID: get_v1_displays_by_id_lint
Overview
Lint a stored display document. Display operations store, validate, resolve, export, and navigate visualization documents used by operator interfaces.
When to use it
- Use it when an application needs to lint a stored display document.
- Use it when a user interface needs to organize, save, validate, or resolve an operational display.
Quick example
Set the base URL and replace generated identifiers or credentials with values from your installation.
cURL
curl --request GET \
--url "$ORDINATE_URL/v1/displays/00000000-0000-4000-8000-000000000001/lint" \
--header "Authorization: Bearer $ORDINATE_TOKEN"Expected output · 200
Non-blocking lint rows
Example 200 output
[
{
"widget_id": "string",
"code": "string",
"message": "string",
"severity": "note"
}
]The cURL request supplies the documented path and query values and asks OrdinateDB to lint a stored display document. The documented 200 response is non-blocking lint rows.
How it works
Display documents are versioned independently from their folders, while resolve and time routes prepare a document for a specific asset and viewing window.
Reference
- Required capability
- read
- Authorization scope
- handler-resolved target
Parameters
| Name | In | Required | Type and constraints |
|---|---|---|---|
id | path | yes | stringformat: uuid |
Request body
This operation has no request body.
Responses
200Non-blocking lint rows
application/json
array
codestringrequiredmessagestringrequiredseveritystringrequiredwidget_idany ofrequiredany of
option 1
stringoption 2
null
Example 200 output
[
{
"widget_id": "string",
"code": "string",
"message": "string",
"severity": "note"
}
]401Authentication required
application/json
ErrorEnvelope
codestringrequiredcorrelation_idstringrequired- format: uuid
detailsobjectoptionalerrorstringrequired
Example 401 output
{
"error": "string",
"code": "account-sealed",
"correlation_id": "00000000-0000-4000-8000-000000000001"
}403read capability is not granted
application/json
ErrorEnvelope
codestringrequiredcorrelation_idstringrequired- format: uuid
detailsobjectoptionalerrorstringrequired
Example 403 output
{
"error": "string",
"code": "account-sealed",
"correlation_id": "00000000-0000-4000-8000-000000000001"
}404Display not found
application/json
ErrorEnvelope
codestringrequiredcorrelation_idstringrequired- format: uuid
detailsobjectoptionalerrorstringrequired
Example 404 output
{
"error": "string",
"code": "account-sealed",
"correlation_id": "00000000-0000-4000-8000-000000000001"
}503Model database is not configured or unavailable
application/json
ErrorEnvelope
codestringrequiredcorrelation_idstringrequired- format: uuid
detailsobjectoptionalerrorstringrequired
Example 503 output
{
"error": "string",
"code": "account-sealed",
"correlation_id": "00000000-0000-4000-8000-000000000001"
}Code examples
These examples are generated from the source contract. Replace the base URL, credentials, identifiers, and minimal generated values for your instance.
JavaScript
const ordinateUrl = "http://localhost:8080";
const token = "<bearer-token>";
const response = await fetch(`${ordinateUrl}/v1/displays/00000000-0000-4000-8000-000000000001/lint`, {
method: "GET",
headers: {
Authorization: `Bearer ${token}`
}
});
if (!response.ok) {
throw new Error(`OrdinateDB returned ${response.status}: ${await response.text()}`);
}
const data = await response.json();
console.log(data);Related topics
- Wire conventions — Understand the prerequisite concepts and transport behavior for this operation.
- REST endpoint index — Find other operations in Displays.