OrdinateDB

Documentation

product Pre-releaseunwritten sections are marked
GET/v1/series

List registered series visible to the caller

operation ID: get_v1_series

Overview

List registered series visible to the caller. Series-storage operations expose registered series, direct stored data, gap and chunk metadata, and lifecycle controls.

When to use it

  • Use it when an application needs to list registered series visible to the caller.
  • Use it when a diagnostic or maintenance tool needs storage-level series data instead of model-resolved attributes.

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/series" \
  --header "Authorization: Bearer $ORDINATE_TOKEN"

Expected output · 200

Series registry entries; unreadable series are absent. The response is a bare array unless cursor or limit activates keyset pagination.

Example 200 output

[
  {
    "series_uuid": "00000000-0000-4000-8000-000000000001",
    "source_uri": "string",
    "staged": false,
    "value_type": "string",
    "writable_class": "standard",
    "rollups_enabled": false
  }
]

The cURL request supplies the documented path and query values and asks OrdinateDB to list registered series visible to the caller. The documented 200 response is series registry entries; unreadable series are absent. The response is a bare array unless cursor or limit activates keyset pagination.

How it works

These routes address a stable series UUID directly. Use resolved-read routes when an application should follow model bindings across time.

Reference

Required capability
read
Authorization scope
held anywhere

Parameters

NameInRequiredType and constraints
cursorqueryno
string

Opaque keyset cursor returned as next_cursor by the preceding page

limitqueryno
integer

Activates the paginated response envelope; values above 1000 are rejected

minimum: 0 · maximum: 1000

Request body

This operation has no request body.

Responses

200Series registry entries; unreadable series are absent. The response is a bare array unless cursor or limit activates keyset pagination.

application/json

one of

option 1

array

rollups_enabledbooleanrequired
series_uuidstringrequired
format: uuid
source_uristringrequired
stagedbooleanrequired
value_typeany ofrequired

any of

option 1

string

option 2

null
writable_classstringrequired
unknown fields rejected

option 2

itemsarrayrequired

array

rollups_enabledbooleanrequired
series_uuidstringrequired
format: uuid
source_uristringrequired
stagedbooleanrequired
value_typeany ofrequired

any of

option 1

string

option 2

null
writable_classstringrequired
unknown fields rejected
next_cursorstringoptional
unknown fields rejected

Example 200 output

[
  {
    "series_uuid": "00000000-0000-4000-8000-000000000001",
    "source_uri": "string",
    "staged": false,
    "value_type": "string",
    "writable_class": "standard",
    "rollups_enabled": false
  }
]
400Invalid cursor or pagination limit above 1000

application/json

ErrorEnvelope
codestringrequired
correlation_idstringrequired
format: uuid
detailsobjectoptional
errorstringrequired

Example 400 output

{
  "error": "string",
  "code": "account-sealed",
  "correlation_id": "00000000-0000-4000-8000-000000000001"
}
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"
}

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