OrdinateDB

Documentation

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

Create an episode

operation ID: post_v1_episodes

Overview

Create an episode. 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.
  • 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" \
  --header "Authorization: Bearer $ORDINATE_TOKEN" \
  --header "Content-Type: application/json" \
  --data '{
    "template": "00000000-0000-4000-8000-000000000001",
    "start_ns": 0
  }'

Expected output · 201

Created episode identity and computed flags

Example 201 output

{
  "id": "00000000-0000-4000-8000-000000000001",
  "version": 0,
  "name": "string",
  "flags": [
    "string"
  ],
  "origin": "trigger"
}

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

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. Overlap, grammar, nesting, and naming violations are stored successfully and reported in flags rather than rejected.
Required capability
episode-manage
Authorization scope
handler-resolved target

Parameters

No parameters.

Request body

application/json

asset_refsarrayoptional

array

asset_idstringrequired
format: uuid
rolestringrequired
unknown fields rejected
attributesobjectoptional
end_nsany ofoptional

any of

option 1

integer

UTC Unix timestamp in nanoseconds

format: int64

option 2

null
originstringoptional
parentany ofoptional

any of

option 1

stringformat: uuid

option 2

null
reasonstringoptional
start_nsintegerrequired

UTC Unix timestamp in nanoseconds

format: int64
templatestringrequired
format: uuid
unknown fields rejected

Example request body

{
  "template": "00000000-0000-4000-8000-000000000001",
  "start_ns": 0
}

Responses

201Created episode identity and computed flags

application/json

flagsarrayrequired

array

string
idstringrequired
format: uuid
namestringrequired
originstringrequired
versionintegerrequired
format: int64
unknown fields rejected

Example 201 output

{
  "id": "00000000-0000-4000-8000-000000000001",
  "version": 0,
  "name": "string",
  "flags": [
    "string"
  ],
  "origin": "trigger"
}
400Invalid episode, time span, template, roles, or attributes

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`, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${token}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
  "template": "00000000-0000-4000-8000-000000000001",
  "start_ns": 0
})
});

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

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