OrdinateDB

Documentation

product Pre-releaseunwritten sections are marked
POST/v1/episodes/templates

Create an episode template

operation ID: post_v1_episodes_templates

Overview

Create an episode template. Episodes represent bounded operational events and the genealogy links between related events.

When to use it

  • Use it when an application needs to create an episode template.
  • 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/templates" \
  --header "Authorization: Bearer $ORDINATE_TOKEN" \
  --header "Content-Type: application/json" \
  --data '{
    "name": "string",
    "family": "string",
    "overlap": "allowed",
    "retro_edit_approval": "none"
  }'

Expected output · 201

Created template identity

Example 201 output

{
  "id": "00000000-0000-4000-8000-000000000001",
  "version": 0
}

The cURL request sends the smallest contract-derived body and asks OrdinateDB to create an episode template. The documented 201 response is created template identity.

How it works

Templates define episode shape, episodes carry event state, and genealogy links connect parent, child, or otherwise related records.

Reference

Wire-format note. retro_edit_approval accepts only `none` in v1; `required` intentionally returns 400 until the approval pipeline exists.
Required capability
episode-manage
Authorization scope
held anywhere

Parameters

No parameters.

Request body

application/json

attributesarrayoptional

array

captureany ofrequired

any of

option 1

string

option 2

null
classstringrequired
enum_setany ofrequired

any of

option 1

string

option 2

null
namestringrequired
quantity_kindany ofrequired

any of

option 1

string

option 2

null
unitany ofrequired

any of

option 1

string

option 2

null
unknown fields rejected
familystringrequired
namestringrequired
naming_patternany ofoptional

any of

option 1

string

option 2

null
overlapstringrequired
permitted_childrenarrayoptional

array

string
reasonstringoptional
retro_edit_approvalstringrequired
rolesarrayoptional

array

cardinalitystringrequired
requiredbooleanrequired
rolestringrequired
unknown fields rejected
triggerany ofoptional

any of

option 1

min_duration_msintegerrequired
format: int64
open_whenstringrequired
unknown fields rejected

option 2

null
unknown fields rejected

Example request body

{
  "name": "string",
  "family": "string",
  "overlap": "allowed",
  "retro_edit_approval": "none"
}

Responses

201Created template identity

application/json

idstringrequired
format: uuid
versionintegerrequired
format: int64
unknown fields rejected

Example 201 output

{
  "id": "00000000-0000-4000-8000-000000000001",
  "version": 0
}
400Invalid template, role, capture, or trigger

application/json

ErrorEnvelope
codestringrequired
correlation_idstringrequired
format: uuid
detailsobjectoptional
errorstringrequired

Example 400 output

{
  "error": "string",
  "code": "account-sealed",
  "correlation_id": "00000000-0000-4000-8000-000000000001"
}
401Authentication required

application/json

ErrorEnvelope
codestringrequired
correlation_idstringrequired
format: uuid
detailsobjectoptional
errorstringrequired

Example 401 output

{
  "error": "string",
  "code": "account-sealed",
  "correlation_id": "00000000-0000-4000-8000-000000000001"
}
403episode-manage capability is not granted

application/json

ErrorEnvelope
codestringrequired
correlation_idstringrequired
format: uuid
detailsobjectoptional
errorstringrequired

Example 403 output

{
  "error": "string",
  "code": "account-sealed",
  "correlation_id": "00000000-0000-4000-8000-000000000001"
}
404Episode or template not found

application/json

ErrorEnvelope
codestringrequired
correlation_idstringrequired
format: uuid
detailsobjectoptional
errorstringrequired

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
codestringrequired
correlation_idstringrequired
format: uuid
detailsobjectoptional
errorstringrequired

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/templates`, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${token}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
  "name": "string",
  "family": "string",
  "overlap": "allowed",
  "retro_edit_approval": "none"
})
});

if (!response.ok) {
  throw new Error(`OrdinateDB returned ${response.status}: ${await response.text()}`);
}

const data = await response.json();
console.log(data);

Related topics