Optionalcontext?: Omit<Omit<{}, "bank">, "authentication"> & { authentication?: unknown }Optionalgovernance_context?: stringOptionalaccount_id?: stringAccount identifier. Present when the response spans or is scoped to a specific account.
Optionalmedia_buy_id?: stringPublisher's media buy identifier. Present when the request was scoped to a single media buy.
ISO 4217 currency code for monetary values in this response (e.g., 'USD', 'EUR')
Date range for the report.
ISO 8601 start timestamp
ISO 8601 end timestamp
Optionaltimezone?: stringIANA timezone identifier for the reporting period (e.g., 'America/New_York', 'UTC'). Platforms report in their native timezone.
Creative delivery data with variant breakdowns
Optionalpagination?: {Pagination information. Present when the request included pagination parameters. Note: get_creative_delivery uses page-based pagination (limit/offset) for historical reasons, distinct from the cursor-based PaginationResponse used by list_* tools. Field naming aligned with PaginationResponse.total_count in 3.1; the legacy total field is retained as a deprecated alias until 4.0. Sellers MUST populate both fields identically; buyers SHOULD prefer total_count (the canonical name) and ignore total if both are present.
Maximum number of creatives requested
Number of creatives skipped
Whether more creatives are available beyond this page
Optionaltotal_count?: numberTotal number of creatives matching the request filters. Canonical field name (matches PaginationResponse.total_count). Sellers SHOULD populate this and the deprecated total field identically until 4.0; buyers SHOULD prefer this field.
Optionaltotal?: numberOptionalerrors?: {Task-specific errors and warnings
Optionalext?: Omit<Omit<{}, "bank">, "authentication"> & { authentication?: unknown }Optionalsummary: string
Governance context token issued by the account's governance agent during check_governance. Buyers attach it to governed purchase requests (media buys, rights acquisitions, signal activations, creative services); sellers persist it and include it on all subsequent governance calls for that action's lifecycle. An account binds to one governance agent (see sync_governance); governance is phased across
purchase/modification/delivery, not partitioned across specialist agents, so the envelope carries a single token for the full lifecycle.Value format: governance agents MUST emit a compact JWS per the AdCP JWS profile (see Security — Signed Governance Context). Sellers MAY verify; sellers that do not verify MUST persist and forward the token unchanged. In 3.1 all sellers MUST verify. Non-JWS values from pre-3.0 governance agents are deprecated.
This is the primary correlation key for audit and reporting across the governance lifecycle.