Skip to main content
Use the Resource History API to show who changed a specific dashboard, automation, monitor, or status page and to restore a prior revision.

​
List audit events

Pass resource_type; for per-page history, also pass resource_id:
Supported resource_type values:
  • dashboard
  • automation
  • monitor
  • status_page
Events include the actor, source surface (dashboard, api, cli, mcp, hosted_agent, automation, or system), source operation, API key name when available, agent run id, model id when provided, summary, metadata, and timestamp. Clients should label an unnamed or deleted key as API key; do not use its key prefix as the actor label.

​
List revisions

Revisions are config snapshots. They are intended for rollback and reapply flows, not runtime telemetry history.

​
Roll back a revision

Rollback restores the selected snapshot and records the rollback as a new audit event and revision.

​
Reapply a revision

Reapply uses the same restore path as rollback, but records the action as reapplied.

​
Agent attribution

Squasher-trusted internal agent and MCP gateways can send attribution headers so history reads cleanly:
When these are present on trusted internal requests, the audit log can show flows such as Jack via MCP or Jack via hosted agent. Public API-key and OAuth requests are recorded as API/CLI callers and cannot claim MCP, hosted-agent, automation, or system attribution through request headers.