Audit Log

{
  "created_ts": "<string>",
  "data": {},
  "type": "<string>",
  "uid": "<string>",
  "api_client_id": "<string>",
  "org_uid": "<string>",
  "schedule_uid": "<string>",
  "schedule_version_uid": "<string>",
  "time_series_uid": "<string>",
  "user_uid": "<string>",
  "version": 1
}

Audit log entries record state changes and actions on schedules, versions, and series. Every significant lifecycle event is captured with before/after state snapshots and request context.

Event types

Event type	Trigger
`schedule.created`	A new schedule is created via `POST /schedules`
`version.submitted`	A schedule version is sent to the TSO
`version.accepted`	TSO ACK or CNF confirms acceptance
`version.rejected`	TSO rejects the submission
`version.status_changed`	Any status transition on a version
`series.status_changed`	Per-series status update from a partial CNF
`anomaly.received`	An ANO message is received from the TSO
`status_request.sent`	A manual status request is triggered

Data structure

The data field is a combined object containing:

before — state snapshot before the event (when applicable)
after — state snapshot after the event
metadata — additional context (e.g. TSO response codes)
request_id — correlation ID for the triggering API request

Timestamp precision

The created_ts field includes millisecond precision (YYYY-MM-DDTHH:mm:ss.sssZ) to allow precise ordering of events that occur in rapid succession.

An audit log entry recording a state change or action on a schedule or series.

created_ts

string

required

ISO 8601 datetime with millisecond precision (YYYY-MM-DDTHH:MM:SS.sssZ).

Example:

"2026-03-25T14:00:00.123Z"

data

Data · object

required

Combined metadata, before/after state snapshots, and request context.

type

string

required

Event type identifier (e.g. schedule.created, version.submitted, version.accepted).

Examples:

"schedule.created"

"version.submitted"

"version.accepted"

uid

string

required

Unique identifier for this audit event.

Example:

"e2f3a4b5-c6d7-4e8f-9a0b-1c2d3e4f5a6b"

api_client_id

string | null

API client identifier that triggered the event, if applicable.

org_uid

string | null

Organization identifier, if applicable.

schedule_uid

string | null

Related Schedule identifier, if applicable.

schedule_version_uid

string | null

Related Schedule Version identifier, if applicable.

time_series_uid

string | null

Related time series identifier, if applicable.

user_uid

string | null

Identifier of the user who triggered the event, if applicable.

version

integer

default:1

Event schema version.

Example:

1

Delivery Status Anomaly

⌘I

Core

Cost of Energy

Power Tariffs

Schedule Management

Settlement Management (MaBiS)

Event types

Data structure

Timestamp precision

Core

Cost of Energy

Power Tariffs

Schedule Management

Settlement Management (MaBiS)

Documentation Index

​Event types

​Data structure

​Timestamp precision

Event types

Data structure

Timestamp precision