{
"created_ts": "2026-03-25T14:00:00.123Z",
"data": {},
"type": "schedule.created",
"uid": "e2f3a4b5-c6d7-4e8f-9a0b-1c2d3e4f5a6b",
"api_client_id": "<string>",
"org_uid": "<string>",
"schedule_uid": "<string>",
"schedule_version_uid": "<string>",
"time_series_uid": "<string>",
"user_uid": "<string>",
"version": 1
}Models
Audit Log
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
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.
ISO 8601 datetime with millisecond precision (YYYY-MM-DDTHH:MM:SS.sssZ).
Example:
"2026-03-25T14:00:00.123Z"
Combined metadata, after-state snapshot, and request context.
Show child attributes
Show child attributes
Event type identifier (e.g. schedule.created).
Examples:
"schedule.created"
"schedule.modified"
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
Was this page helpful?