/v1/model/bindingsBind, rebind, unbind, or splice-revert a series
operation ID: post_v1_model_bindings
Overview
Bind, rebind, unbind, or splice-revert a series. 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 bind, rebind, unbind, or splice-revert a series.
- 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 POST \
--url "$ORDINATE_URL/v1/model/bindings" \
--header "Authorization: Bearer $ORDINATE_TOKEN" \
--header "Content-Type: application/json" \
--data '{
"op": "bind",
"attribute": "00000000-0000-4000-8000-000000000001",
"series": "00000000-0000-4000-8000-000000000001"
}'Expected output · 200
Binding transaction
Example 200 output
{
"tx_id": 0
}The cURL request sends the smallest contract-derived body and asks OrdinateDB to bind, rebind, unbind, or splice-revert a series. The documented 200 response is binding transaction.
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
No parameters.
Request body
application/json
one of
option 1
attributestringrequired- format: uuid
effective_from_nsintegeroptionalUTC Unix timestamp in nanoseconds
format: int64opstringrequiredreasonstringoptionalseriesstringrequired- format: uuid
option 2
at_nsintegerrequiredUTC Unix timestamp in nanoseconds
format: int64attributestringrequired- format: uuid
new_seriesstringrequired- format: uuid
opstringrequiredreasonstringoptional
option 3
at_nsintegerrequiredUTC Unix timestamp in nanoseconds
format: int64attributestringrequired- format: uuid
opstringrequiredreasonstringoptional
option 4
opstringrequiredreasonstringoptionaltx_idintegerrequired- format: int64
Example request body
{
"op": "bind",
"attribute": "00000000-0000-4000-8000-000000000001",
"series": "00000000-0000-4000-8000-000000000001"
}Responses
200Binding transaction
application/json
tx_idintegerrequired- format: int64
Example 200 output
{
"tx_id": 0
}400Invalid or inapplicable binding operation
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"
}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"
}404Binding target 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"
}409Binding overlap, conflict, or superseded splice
application/json
ErrorEnvelope
codestringrequiredcorrelation_idstringrequired- format: uuid
detailsobjectoptionalerrorstringrequired
Example 409 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/bindings`, {
method: "POST",
headers: {
Authorization: `Bearer ${token}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"op": "bind",
"attribute": "00000000-0000-4000-8000-000000000001",
"series": "00000000-0000-4000-8000-000000000001"
})
});
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.