Skip to main content
The Compliance domain exports the deployment’s audit trail for auditors. Three read operations cover a window of at most 90 days:
  • GET /api/v3/compliance-export-audit — exportAuditEvents — page the deployment’s audit events
  • GET /api/v3/compliance-export-governance — exportGovernanceDecisions — page the deployment’s governance decision records
  • GET /api/v3/compliance-export-summary — exportComplianceSummary — count the deployment’s audit events and decisions

Who can export

Compliance exports cover the whole deployment, so they require audit:read granted at the deployment root; a credential granted only below it receives 403. A key or External App holding audit:read at a tenant org unit, or at a partner organization’s own root, gets 403 permission_denied with requiredPermission: "audit:read", and the refusal is recorded as an authorization denial. Platform-scope grants and every migrated key’s root compatibility grant keep the exports. The credential’s scopes must also reach audit:read. An organization that wants its own decisions reads the organization-scoped governance reports and recorded evidence instead.

What a record contains

Each exported record is the stored row as written, with a stable id. Records keep their recorded principal, and the audit export includes events about people. Machine reads elsewhere never return a person’s identity; the compliance exports are the exception, because their reader is a deployment-root auditor whose purpose is the audit trail. No Forge MCP tool exposes these exports: bulk audit records do not belong in a model transcript.

Paging and completeness

  • Window. startTime and endTime are epoch-millisecond integers, startTime < endTime, at most 90 days apart. Make several requests for a longer period.
  • Pages. limit is 1 to 1,000 (default 100). Follow cursor until it is null; send it back unchanged. A governance page can hold fewer records than limit, or none, before the end.
  • Governance pages are bounded. A governance page reads a bounded number of records, so a large window is paged to its end instead of ending early. When more records share one millisecond than a page can read, the page carries partial: true and saturatedAt (that millisecond): the rest of that millisecond is skipped, and cursor continues below it. Narrowing the window cannot split one millisecond.
  • Summary ceiling. summary.capped is true when a source hit its read ceiling; the counts are then a lower bound.
  • Client-reported denials. Console-reported denials are left out of the governance export and the summary unless you pass includeClientReported=true (see Audit).