/v1/model/attributes/{uuid}Retire an attribute instance
operation ID: patch_v1_model_attributes_by_uuid
Overview
Retire an attribute instance. 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 retire an attribute instance.
- 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 PATCH \
--url "$ORDINATE_URL/v1/model/attributes/00000000-0000-4000-8000-000000000001" \
--header "Authorization: Bearer $ORDINATE_TOKEN" \
--header "Content-Type: application/json" \
--data '{}'Expected output · 200
Current or retired attribute
Example 200 output
{
"attribute_id": "00000000-0000-4000-8000-000000000001",
"asset_id": "00000000-0000-4000-8000-000000000001",
"attr_def_id": "00000000-0000-4000-8000-000000000001",
"name": "string",
"overrides": {},
"retired": false,
"tx_id": 0
}The cURL request sends the smallest contract-derived body and asks OrdinateDB to retire an attribute instance. The documented 200 response is current or retired 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
- model-edit
- Authorization scope
- handler-resolved target
Parameters
| Name | In | Required | Type and constraints |
|---|---|---|---|
uuid | path | yes | stringformat: uuid |
Request body
application/json
reasonstringoptionalretirebooleanoptional
Example request body
{}Responses
200Current or retired attribute
application/json
asset_idstringrequired- format: uuid
attr_def_idany ofrequiredany of
option 1
stringformat: uuidoption 2
nullattribute_idstringrequired- format: uuid
namestringrequiredoverridesany ofrequiredArbitrary JSON value
any of
option 1
object with arbitrary properties
option 2
array
any itemsoption 3
stringoption 4
numberoption 5
integeroption 6
booleanoption 7
nullretiredbooleanrequiredtx_idintegerrequired- format: int64
Example 200 output
{
"attribute_id": "00000000-0000-4000-8000-000000000001",
"asset_id": "00000000-0000-4000-8000-000000000001",
"attr_def_id": "00000000-0000-4000-8000-000000000001",
"name": "string",
"overrides": {},
"retired": false,
"tx_id": 0
}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"
}403Model edit 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"
}404Attribute 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/model/attributes/00000000-0000-4000-8000-000000000001`, {
method: "PATCH",
headers: {
Authorization: `Bearer ${token}`,
"Content-Type": "application/json"
},
body: JSON.stringify({})
});
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 Model.