Optionalcontext?: Omit<Omit<{}, "bank">, "authentication"> & { authentication?: unknown }Optionalgovernance_context?: stringSummary of the query that was executed
Total number of creatives matching filters (across all pages)
Number of creatives returned in this response
Optionalfilters_applied?: string[]List of filters that were applied to the query
Optionalsort_applied?: { field?: string; direction?: SortDirection }Sort order that was applied
Whether more results are available beyond this page
Optionalcursor?: stringOpaque cursor to pass in the next request to fetch the next page. Only present when has_more is true.
Optionaltotal_count?: numberTotal number of items matching the query across all pages. Optional because not all backends can efficiently compute this.
Array of creative assets matching the query
Optionalformat_summary?: Omit<Omit<{ [key: string]: number | undefined }, "bank">, "authentication"> & {Breakdown of creatives by canonical format kind. Keys SHOULD be format_kind values; an implementation may append a stable option suffix when separate product or publisher options must be distinguished.
Optionalstatus_summary?: {Breakdown of creatives by status
Optionalprocessing?: numberNumber of creatives being processed
Optionalapproved?: numberNumber of approved creatives
Optionalpending_review?: numberNumber of creatives pending review
Optionalrejected?: numberNumber of rejected creatives
Optionalarchived?: numberNumber of archived creatives
Optionalerrors?: {Task-specific errors (e.g., invalid filters, account not found)
Optionalsandbox?: booleanWhen true, this response contains simulated data from sandbox mode.
Optionalext?: Omit<Omit<{ [key: string]: unknown }, "bank">, "authentication"> & {Optionalsummary: string
Opaque authorization context issued only by an approved check_governance decision. Buyers attach it to governed requests across protocol roles (media buys, rights acquisitions, signal activations, creative services); receiving services persist it and forward it on subsequent execution and lifecycle checks. The context is the authoritative plan binding at service boundaries, so a service MUST NOT require a separate plan_id.
Governance agents MUST emit a compact JWS per the AdCP JWS profile. Verifiers validate standard authorization claims such as signature, issuer, audience, expiry, and replay protection, but intermediaries MUST NOT interpret embedded governance state for business logic. A conditions or denied verdict never carries an authorization context.
This is the primary correlation key for audit and reporting across the governance lifecycle.