Skip to main content
Audit log entries record state changes and actions on schedules, clearing periods, and market messages. Each entry captures the state after the event, who triggered it, and the labels carried with it.

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.

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, after-state snapshot, and request context.

type
string
required

Event type identifier (e.g. schedule.created).

Examples:

"schedule.created"

"schedule.modified"

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