List views

Overview

List views. The model API describes assets, attributes, bindings, templates, views, registries, and governed changes that give series data its operational meaning.

When to use it

• Use it when an application needs to list views.
• Use it when a modeling tool is building, governing, resolving, or inspecting the asset and attribute hierarchy.

Quick example

Set the base URL and replace generated identifiers or credentials with values from your installation.

curl --request GET \
  --url "$ORDINATE_URL/v1/model/views" \
  --header "Authorization: Bearer $ORDINATE_TOKEN"

[
  {
    "view_id": "00000000-0000-4000-8000-000000000001",
    "name": "string",
    "retired": false,
    "tx_id": 0
  }
]

The cURL request supplies the documented path and query values and asks OrdinateDB to list views. The documented 200 response is views.

How it works

Reference

Required capability

read

Authorization scope

held anywhere

[
  {
    "view_id": "00000000-0000-4000-8000-000000000001",
    "name": "string",
    "retired": false,
    "tx_id": 0
  }
]

{
  "error": "string",
  "code": "account-sealed",
  "correlation_id": "00000000-0000-4000-8000-000000000001"
}

{
  "error": "string",
  "code": "account-sealed",
  "correlation_id": "00000000-0000-4000-8000-000000000001"
}

{
  "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.

const ordinateUrl = "http://localhost:8080";
const token = "<bearer-token>";

const response = await fetch(`${ordinateUrl}/v1/model/views`, {
  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);