Skip to main content

get_plan_audit_logs

Experimental. Campaign governance (sync_plans, check_governance, report_plan_outcome, report_plan_adjustment, get_plan_audit_logs) is part of AdCP 3.0 as an experimental surface — it may change between 3.x releases with at least 6 weeks’ notice. Sellers implementing it MUST declare governance.campaign in experimental_features. See experimental status for the full contract.
Retrieve governance state and audit trail for a plan, multiple plans, or an entire portfolio. Returns budget tracking, validation history, and compliance summary. Budget state separates gross_committed, adjustments_reported, adjustments_verified, economic net_cost, headroom_restored, and ledger_committed. The legacy committed and net_committed fields remain 3.x aliases for the current ledger value. Adjustment entries are append-only; they never rewrite the source outcome or decrement the trailing aggregate used for fragmentation defense.

Request

Results are joined by the governance agent’s stable opaque action binding. The exposed governance_context is the original intent context for correlation; later lifecycle checks have freshly signed context strings but remain part of the same action. Multiple plans — retrieve specific plans in one call:
Portfolio query — retrieve combined audit data for all member plans in one or more portfolios:
You can combine plan_ids and portfolio_plan_ids to query both specific plans and portfolios in a single call.

Response

Fields

Request

Response

Authorization

The request schema does not carry an envelope account field — tenant identity is resolved from the submitted IDs. The governance agent MUST verify that the authenticated principal is authorized for every plan_ids member, every plan expanded from portfolio_plan_ids, and every governed action addressed by governance_contexts. When any element fails the authorization check the governance agent MUST fail closed with a generic PLAN_NOT_FOUND response — the error body MUST NOT distinguish “unauthorized” from “not found” or name the offending ID. See Agent and Account Isolation for the pattern and existence-leak guardrails.

Error codes