/v1/model/calc/rules/{id}Create a new calculation rule version
operation ID: put_v1_model_calc_rules_by_id
Overview
Create a new calculation rule version. 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 create a new calculation rule version.
- 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 PUT \
--url "$ORDINATE_URL/v1/model/calc/rules/00000000-0000-4000-8000-000000000001?recompute=history" \
--header "Authorization: Bearer $ORDINATE_TOKEN" \
--header "Content-Type: application/json" \
--data '{
"name": "string",
"scope": {
"template_id": "00000000-0000-4000-8000-000000000001",
"output_attr_def_id": "00000000-0000-4000-8000-000000000001"
},
"tier": "expression",
"trigger": {
"kind": "event"
},
"unit_check": "strict",
"provisional": "block"
}'Expected output · 200
Updated rule identity and version
Example 200 output
{
"rule_id": "00000000-0000-4000-8000-000000000001",
"version": 0
}The cURL request sends the smallest contract-derived body and asks OrdinateDB to create a new calculation rule version. The documented 200 response is updated rule identity and version.
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
- calc-author
- Authorization scope
- handler-resolved target
Parameters
| Name | In | Required | Type and constraints |
|---|---|---|---|
id | path | yes | stringformat: uuid |
recompute | query | yes | stringvalues: history · from-now |
Request body
application/json
declared_inferredbooleanoptionalexpressionany ofoptionalany of
option 1
stringoption 2
nullnamestringrequiredprovisionalstringrequiredreasonstringoptionalscopeone ofrequiredone of
option 1
output_attr_def_idstringrequired- format: uuid
template_idstringrequired- format: uuid
option 2
asset_idstringrequired- format: uuid
output_attribute_idstringrequired- format: uuid
tierstringrequiredtriggerone ofrequiredone of
option 1
debounce_msany ofoptionalany of
option 1
integerformat: int64option 2
nullkindstringrequired
option 2
alignany 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
nullinterval_nsintegerrequired- format: int64
kindstringrequired
option 3
edgestringrequiredexprstringrequiredkindstringrequired
unit_checkstringrequiredwhenany ofoptionalany of
option 1
stringoption 2
null
Example request body
{
"name": "string",
"scope": {
"template_id": "00000000-0000-4000-8000-000000000001",
"output_attr_def_id": "00000000-0000-4000-8000-000000000001"
},
"tier": "expression",
"trigger": {
"kind": "event"
},
"unit_check": "strict",
"provisional": "block"
}Responses
200Updated rule identity and version
application/json
rule_idstringrequired- format: uuid
versionintegerrequired- format: int64
Example 200 output
{
"rule_id": "00000000-0000-4000-8000-000000000001",
"version": 0
}400Missing recompute or invalid rule
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"
}403calc-author 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"
}404Rule 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/calc/rules/00000000-0000-4000-8000-000000000001?recompute=history`, {
method: "PUT",
headers: {
Authorization: `Bearer ${token}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"name": "string",
"scope": {
"template_id": "00000000-0000-4000-8000-000000000001",
"output_attr_def_id": "00000000-0000-4000-8000-000000000001"
},
"tier": "expression",
"trigger": {
"kind": "event"
},
"unit_check": "strict",
"provisional": "block"
})
});
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.