OrdinateDB

Documentation

product Pre-releaseunwritten sections are marked
GET/v1/model/attributes/{uuid}

Read an effective attribute

operation ID: get_v1_model_attributes_by_uuid

Overview

Read an effective attribute. 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 read an effective attribute.
  • 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

curl --request GET \
  --url "$ORDINATE_URL/v1/model/attributes/00000000-0000-4000-8000-000000000001" \
  --header "Authorization: Bearer $ORDINATE_TOKEN"

Expected output · 200

Effective attribute

Example 200 output

{
  "attribute_id": "00000000-0000-4000-8000-000000000001",
  "asset_id": "00000000-0000-4000-8000-000000000001",
  "name": "string",
  "attr_def_id": "00000000-0000-4000-8000-000000000001",
  "quantity_kind_id": "00000000-0000-4000-8000-000000000001",
  "display_unit_id": "00000000-0000-4000-8000-000000000001",
  "continuity_class": "continuous",
  "writer_class": "collector",
  "enum_set_id": "00000000-0000-4000-8000-000000000001",
  "limit_traits": {},
  "lifecycle_policy": {},
  "entry_cadence": {},
  "retired": false,
  "overridden_fields": [
    "string"
  ]
}

The cURL request supplies the documented path and query values and asks OrdinateDB to read an effective attribute. The documented 200 response is effective attribute.

How it works

Assets form the composition hierarchy, attributes describe values on those assets, and time-bounded bindings connect attributes to stored series.

Reference

Required capability
read
Authorization scope
handler-resolved target

Parameters

NameInRequiredType and constraints
uuidpathyes
stringformat: uuid
as_of_nsqueryno
integer

UTC Unix timestamp in nanoseconds

format: int64

Request body

This operation has no request body.

Responses

200Effective attribute

application/json

asset_idstringrequired
format: uuid
attr_def_idany ofrequired

any of

option 1

stringformat: uuid

option 2

null
attribute_idstringrequired
format: uuid
continuity_classstringrequired
display_unit_idany ofrequired

any of

option 1

stringformat: uuid

option 2

null
entry_cadenceany ofrequired

any of

option 1

any of

option 1

object with arbitrary properties

option 2

array

any items

option 3

string

option 4

number

option 5

integer

option 6

boolean

option 7

null

option 2

null
enum_set_idany ofrequired

any of

option 1

stringformat: uuid

option 2

null
lifecycle_policyany ofrequired

any of

option 1

any of

option 1

object with arbitrary properties

option 2

array

any items

option 3

string

option 4

number

option 5

integer

option 6

boolean

option 7

null

option 2

null
limit_traitsany ofrequired

Arbitrary JSON value

any of

option 1

object with arbitrary properties

option 2

array

any items

option 3

string

option 4

number

option 5

integer

option 6

boolean

option 7

null
namestringrequired
overridden_fieldsarrayrequired

array

string
quantity_kind_idany ofrequired

any of

option 1

stringformat: uuid

option 2

null
retiredbooleanrequired
writer_classstringrequired
unknown fields rejected

Example 200 output

{
  "attribute_id": "00000000-0000-4000-8000-000000000001",
  "asset_id": "00000000-0000-4000-8000-000000000001",
  "name": "string",
  "attr_def_id": "00000000-0000-4000-8000-000000000001",
  "quantity_kind_id": "00000000-0000-4000-8000-000000000001",
  "display_unit_id": "00000000-0000-4000-8000-000000000001",
  "continuity_class": "continuous",
  "writer_class": "collector",
  "enum_set_id": "00000000-0000-4000-8000-000000000001",
  "limit_traits": {},
  "lifecycle_policy": {},
  "entry_cadence": {},
  "retired": false,
  "overridden_fields": [
    "string"
  ]
}
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"
}
404Attribute not found

application/json

ErrorEnvelope
codestringrequired
correlation_idstringrequired
format: uuid
detailsobjectoptional
errorstringrequired

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
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/model/attributes/00000000-0000-4000-8000-000000000001`, {
  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