/v1/episodes/{id}/closeClose an open episode
operation ID: post_v1_episodes_by_id_close
Overview
Close an open episode. Episodes represent bounded operational events and the genealogy links between related events.
When to use it
- Use it when an application needs to close an open episode.
- Use it when an application tracks an incident, batch, excursion, or other event interval and its relationships.
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/episodes/00000000-0000-4000-8000-000000000001/close" \
--header "Authorization: Bearer $ORDINATE_TOKEN" \
--header "Content-Type: application/json" \
--data '{
"end_ns": 0
}'Expected output · 200
New closed episode version
Example 200 output
{
"version": 0
}The cURL request sends the smallest contract-derived body and asks OrdinateDB to close an open episode. The documented 200 response is new closed episode version.
How it works
Templates define episode shape, episodes carry event state, and genealogy links connect parent, child, or otherwise related records.
Reference
- Required capability
- episode-manage
- Authorization scope
- handler-resolved target
Parameters
| Name | In | Required | Type and constraints |
|---|---|---|---|
id | path | yes | stringformat: uuid |
Request body
application/json
end_nsintegerrequiredUTC Unix timestamp in nanoseconds
format: int64reasonstringoptional
Example request body
{
"end_ns": 0
}Responses
200New closed episode version
application/json
versionintegerrequired- format: int64
Example 200 output
{
"version": 0
}400Invalid close time
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"
}403episode-manage 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"
}404Episode or template 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/episodes/00000000-0000-4000-8000-000000000001/close`, {
method: "POST",
headers: {
Authorization: `Bearer ${token}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"end_ns": 0
})
});
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 Episodes.