/v1/annotations/attachmentsUpload an annotation attachment
operation ID: post_v1_annotations_attachments
Overview
Upload an annotation attachment. 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 upload an annotation attachment.
- 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 POST \
--url "$ORDINATE_URL/v1/annotations/attachments?name=string&mime=string" \
--header "Authorization: Bearer $ORDINATE_TOKEN" \
--header "Content-Type: application/octet-stream" \
--data-binary "@request-body.bin"Expected output · 201
Content-addressed upload receipt
Example 201 output
{
"attachment_id": "00000000-0000-4000-8000-000000000001",
"size_bytes": 0,
"content_hash": "string",
"deduplicated": false
}The cURL request sends the smallest contract-derived body and asks OrdinateDB to upload an annotation attachment. The documented 201 response is content-addressed upload receipt.
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
- annotate
- Authorization scope
- handler-resolved target
Parameters
| Name | In | Required | Type and constraints |
|---|---|---|---|
name | query | yes | string |
mime | query | yes | string |
Request body
application/octet-stream
stringformat: binaryResponses
201Content-addressed upload receipt
application/json
attachment_idstringrequired- format: uuid
content_hashstringrequireddeduplicatedbooleanrequiredsize_bytesintegerrequired- format: int64
Example 201 output
{
"attachment_id": "00000000-0000-4000-8000-000000000001",
"size_bytes": 0,
"content_hash": "string",
"deduplicated": false
}400Missing upload metadata
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"
}403annotate 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"
}413Attachment exceeds configured byte cap
application/json
ErrorEnvelope
codestringrequiredcorrelation_idstringrequired- format: uuid
detailsobjectoptionalerrorstringrequired
Example 413 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/attachments?name=string&mime=string`, {
method: "POST",
headers: {
Authorization: `Bearer ${token}`,
"Content-Type": "application/octet-stream"
},
body: requestBody
});
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.