/v1/series/{uuid}/chunksList storage chunks for a series and range
operation ID: get_v1_series_by_uuid_chunks
Overview
List storage chunks for a series and range. 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 storage chunks for a series and range.
- 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/00000000-0000-4000-8000-000000000001/chunks?start_ns=0&end_ns=0" \
--header "Authorization: Bearer $ORDINATE_TOKEN"Expected output · 200
Chunk diagnostics
Example 200 output
[
{
"chunk_id": 0,
"space": "string",
"tier": "string",
"format_version": 0,
"t_min": 0,
"t_max": 0,
"count": 0,
"has_revisions": false,
"lossy_tag": "string",
"state": "string"
}
]The cURL request supplies the documented path and query values and asks OrdinateDB to list storage chunks for a series and range. The documented 200 response is chunk diagnostics.
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
- owning asset of series path parameter `uuid`, or staging-root
Parameters
| Name | In | Required | Type and constraints |
|---|---|---|---|
uuid | path | yes | stringformat: uuid |
start_ns | query | yes | integerUTC Unix timestamp in nanoseconds format: int64 |
end_ns | query | yes | integerUTC Unix timestamp in nanoseconds format: int64 |
Request body
This operation has no request body.
Responses
200Chunk diagnostics
application/json
array
chunk_idintegerrequired- format: int64
countintegerrequired- minimum: 0
format_versionintegerrequired- minimum: 0
has_revisionsbooleanrequiredlossy_tagstringrequiredspacestringrequiredstatestringrequiredt_maxintegerrequiredUTC Unix timestamp in nanoseconds
format: int64t_minintegerrequiredUTC Unix timestamp in nanoseconds
format: int64tierstringrequired
Example 200 output
[
{
"chunk_id": 0,
"space": "string",
"tier": "string",
"format_version": 0,
"t_min": 0,
"t_max": 0,
"count": 0,
"has_revisions": false,
"lossy_tag": "string",
"state": "string"
}
]400Invalid UUID or range
application/json
ErrorEnvelope
codestringrequiredcorrelation_idstringrequired- format: uuid
detailsobjectoptionalerrorstringrequired
Example 400 output
{
"error": "string",
"code": "account-sealed",
"correlation_id": "00000000-0000-4000-8000-000000000001"
}text/plain
string401Authentication 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"
}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/00000000-0000-4000-8000-000000000001/chunks?start_ns=0&end_ns=0`, {
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 Series storage.