/v1/annotations/{id}/versionsList annotation versions
operation ID: get_v1_annotations_by_id_versions
Overview
List annotation versions. Annotations attach human context and evidence to operational data without changing the recorded series values.
When to use it
- Use it when an application needs to list annotation versions.
- Use it when an operator needs to add, find, revise, or preserve context around an event or time range.
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/annotations/00000000-0000-4000-8000-000000000001/versions" \
--header "Authorization: Bearer $ORDINATE_TOKEN"Expected output · 200
Version history including redaction reasons
Example 200 output
{
"versions": [
{}
]
}The cURL request supplies the documented path and query values and asks OrdinateDB to list annotation versions. The documented 200 response is version history including redaction reasons.
How it works
Annotations are versioned records. Content can be revised or redacted while the API retains the documented history and attachment relationships.
Reference
- Required capability
- read
- Authorization scope
- handler-resolved target
Parameters
| Name | In | Required | Type and constraints |
|---|---|---|---|
id | path | yes | stringformat: uuid |
Request body
This operation has no request body.
Responses
200Version history including redaction reasons
application/json
versionsarrayrequiredarray
object with arbitrary properties
Example 200 output
{
"versions": [
{}
]
}400Invalid annotation id
application/json
ErrorEnvelope
codestringrequiredcorrelation_idstringrequired- format: uuid
detailsobjectoptionalerrorstringrequired
Example 400 output
{
"error": "string",
"code": "account-sealed",
"correlation_id": "00000000-0000-4000-8000-000000000001"
}401Authentication 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"
}404Annotation not found
application/json
ErrorEnvelope
codestringrequiredcorrelation_idstringrequired- format: uuid
detailsobjectoptionalerrorstringrequired
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
codestringrequiredcorrelation_idstringrequired- format: uuid
detailsobjectoptionalerrorstringrequired
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/annotations/00000000-0000-4000-8000-000000000001/versions`, {
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 Annotations.