v8.0.0-beta.2
Pre-release
Pre-release
AdCP Python SDK 8.0.0-beta.2
SDK 8 beta release notes are cumulative. If you are upgrading from SDK 7.x, read both migration guides before deploying:
Breaking changes inherited from beta.1
ADCPClient.handle_webhook()no longer accepts unsigned MCP callbacks by default. Configurewebhook_secretfor the legacy HMAC path, or useWebhookReceiverfor RFC 9421 verification and delivery deduplication.allow_unauthenticated_webhooks=Trueis a temporary compatibility escape hatch only for endpoints isolated from untrusted networks; multi-agent clients must scope it by agent ID.- SDK 8 aligns its safety and asset APIs with JavaScript SDK v13, including the public
AssetInstancediscriminated union and stable Python*Contentvariant names.
See beta.1 / PR #1032 for the complete breaking-change rationale.
Added in beta.2
- Bundles AdCP
3.2.0-beta.0schemas and exposes the compact lifecycle across the client, multi-client, MCP, A2A, server handlers/builders, decisioning framework, and CLI:list_productsrequest_proposalsrefine_proposalsdecline_proposalsbuy_productsaccept_proposalcontrol_media_buy
- Adds
report_plan_adjustmentandsync_agent_notification_configs. - Adds compatibility coverage for 3.0 legacy, 3.1 legacy, 3.2 legacy lifecycle, 3.2 direct purchase, and 3.2 proposal purchase.
- Implements the strict AdCP 3.2 RFC 9421 signing profile. A 3.0/3.1 peer currently requires
SigningConfig(signing_profile_version="3.1"); see the migration guide.
Proposal support boundary
Beta.2 provides the typed lifecycle primitives and transport/server dispatch needed to list products, request/refine/decline proposals, buy directly, accept a proposal, and control a media buy.
The richer negotiation layer—capability-aware builders, constraint and lineage verification, digest checking, batch preflight/rollback helpers, and complete buyer/seller orchestration examples—remains tracked in #1023. Do not interpret the beta.2 lifecycle primitives as completion of that higher-level validation framework.