OrdinateDB

Documentation

product Pre-releaseunwritten sections are marked
GET/v1/display-folders

List child display folders

operation ID: get_v1_display_folders

Overview

List child display folders. 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 list child display folders.
  • 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/display-folders" \
  --header "Authorization: Bearer $ORDINATE_TOKEN"

Expected output · 200

Folders directly beneath the selected parent

Example 200 output

[
  {
    "folder_id": "00000000-0000-4000-8000-000000000001",
    "parent_id": "00000000-0000-4000-8000-000000000001",
    "name": "string",
    "tx_id": 0
  }
]

The cURL request supplies the documented path and query values and asks OrdinateDB to list child display folders. The documented 200 response is folders directly beneath the selected parent.

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

NameInRequiredType and constraints
parentqueryno
stringformat: uuid

Request body

This operation has no request body.

Responses

200Folders directly beneath the selected parent

application/json

array

folder_idstringrequired
format: uuid
namestringrequired
parent_idany ofrequired

any of

option 1

stringformat: uuid

option 2

null
tx_idintegerrequired
format: int64
unknown fields rejected

Example 200 output

[
  {
    "folder_id": "00000000-0000-4000-8000-000000000001",
    "parent_id": "00000000-0000-4000-8000-000000000001",
    "name": "string",
    "tx_id": 0
  }
]
401Authentication required

application/json

ErrorEnvelope
codestringrequired
correlation_idstringrequired
format: uuid
detailsobjectoptional
errorstringrequired

Example 401 output

{
  "error": "string",
  "code": "account-sealed",
  "correlation_id": "00000000-0000-4000-8000-000000000001"
}
403read capability is not granted

application/json

ErrorEnvelope
codestringrequired
correlation_idstringrequired
format: uuid
detailsobjectoptional
errorstringrequired

Example 403 output

{
  "error": "string",
  "code": "account-sealed",
  "correlation_id": "00000000-0000-4000-8000-000000000001"
}
503Model database is not configured or unavailable

application/json

ErrorEnvelope
codestringrequired
correlation_idstringrequired
format: uuid
detailsobjectoptional
errorstringrequired

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/display-folders`, {
  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);