Models
Audit Log
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
Thedata field is a combined object containing:
before— state snapshot before the event (when applicable)after— state snapshot after the eventmetadata— additional context (e.g. TSO response codes)request_id— correlation ID for the triggering API request
Timestamp precision
Thecreated_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.
ISO 8601 datetime with millisecond precision (YYYY-MM-DDTHH:MM:SS.sssZ).
Example:
"2026-03-25T14:00:00.123Z"
Combined metadata, before/after state snapshots, and request context.
Event type identifier (e.g. schedule.created, version.submitted, version.accepted).
Examples:
"schedule.created"
"version.submitted"
"version.accepted"
Unique identifier for this audit event.
Example:
"e2f3a4b5-c6d7-4e8f-9a0b-1c2d3e4f5a6b"
API client identifier that triggered the event, if applicable.
Organization identifier, if applicable.
Related Schedule Version identifier, if applicable.
Related time series identifier, if applicable.
Identifier of the user who triggered the event, if applicable.
Event schema version.
Example:
1