- Manual Mode: Provide
packagesarray with explicit line item configurations - Proposal Mode: Provide
proposal_idandtotal_budgetto execute a proposal fromget_products
completed, working < 120s, or submitted for hours/days)
Request Schema: /schemas/v2/media-buy/create-media-buy-request.json
Response Schema: /schemas/v2/media-buy/create-media-buy-response.json
Quick Start
Create a simple media buy with two packages:Request Parameters
* Either
packages OR (proposal_id + total_budget) must be provided.
TotalBudget Object
Package Object
Response
Success Response
Error Response
Note: Responses use discriminated unions - you get either success fields OR errors, never both. Always check for
errors before accessing success fields.
Common Scenarios
Campaign with Targeting
Add geographic restrictions and frequency capping:Campaign with Conversion Optimization
Set a per_ad_spend target for conversion-optimized delivery. The product must declare support inconversion_tracking.supported_targets, and you must have an event source configured via sync_event_sources:
Catalog-driven packages
A catalog-driven package allocates a single budget envelope to an entire catalog of items. Instead of creating separate packages per item, the platform optimizes delivery across all catalog items based on performance. This is the AdCP equivalent of catalog-based campaign types such as Google Performance Max or Meta Dynamic Product Ads. Include thecatalogs field in a package to make it catalog-driven. Each catalog should have a distinct type (e.g., one product catalog, one store catalog). The referenced catalogs must already be synced via sync_catalogs.
Job campaign with synced job catalog:
test=false
test=false
get_media_buy_delivery which returns by_catalog_item breakdowns. Creative variants for catalog-driven packages represent individual catalog items rendered as ads.
Campaign with Inline Creatives
Upload creatives at the same time as creating the campaign:Campaign with Reporting Webhook
Receive automated reporting notifications:Executing a Proposal
Execute a proposal fromget_products without manually constructing packages:
- The publisher converts allocation percentages to actual budgets using
total_budget - Packages are created automatically based on the proposal’s allocations
- All other fields (brand, start_time, end_time, etc.) work the same as manual mode
Error Handling
Common errors and resolutions:
Example error response:
Key Concepts
Format Specification
Format IDs are required for each package because:- Publishers create placeholder creatives in ad servers
- Both parties know exactly what creative assets are needed
- Validation ensures products support requested formats
- Progress tracking shows which assets are missing
Brand reference
Thebrand field identifies the advertiser for policy compliance and business purposes.
Pricing & Currency
Each package specifies itspricing_option_id, which determines:
- Currency (USD, EUR, etc.)
- Pricing model (CPM, CPCV, CPP, etc.)
- Rate and whether it’s fixed or auction-based
Targeting Overlays
Use sparingly - most targeting should be in your brief and handled through product selection. Use overlays only for:- Geographic restrictions (RCT testing, regulatory compliance)
- Frequency capping
- AXE segment inclusion/exclusion
Format Workflow
Why Format Specification Matters
When creating a media buy, format specification enables:- Placeholder Creation - Publisher creates placeholders in ad server with correct specs
- Validation - System validates products support requested formats
- Clear Expectations - Both parties know exactly what’s needed
- Progress Tracking - Track which assets are missing vs. required
- Technical Setup - Ad server configured before creatives arrive
Complete Workflow
Format Validation
Publishers MUST validate:- All formats are supported by the product
- Format specifications match
list_creative_formatsoutput - Creative requirements can be fulfilled within timeline
Flight date validation
When a package specifiesstart_time or end_time, sellers SHOULD validate that:
- Both dates fall within the media buy’s date range
start_timeis beforeend_time
INVALID_REQUEST error:
Asynchronous Operations
This task can complete instantly or take days depending on complexity and approval requirements. The response includes astatus field that tells you what happened and what to do next.
Note: For the complete status list see Task Lifecycle.
- MCP
- A2A
Immediate Success (completed)
The task completed synchronously. No async handling needed.Request:test=false
Long-Running (submitted)
The task is queued for manual approval. Configure a webhook to receive updates.Request with webhook:test=false
Error (failed)
Response:Usage Notes
- Total budget is distributed across packages based on individual
budgetvalues - Both media buys and packages have
buyer_reffields for tracking - Creative assets must be uploaded before deadline for campaign activation
- AXE segments enable advanced audience targeting
- Pending states (
working,submitted) are normal, not errors - Orchestrators MUST handle pending states as part of normal workflow
- Inline creatives: The
creativesarray creates NEW creatives only. To update existing creatives, usesync_creatives. To assign existing library creatives, usecreative_assignmentsinstead.
Policy Compliance
Brand and products are validated during creation. Policy violations return errors:- Brand/products align with selected packages
- Creatives match declared brand/products
- Campaign complies with all advertising policies
Next Steps
After creating a media buy:- Upload Creatives: Use
sync_creativesbefore deadline - Monitor Status: Use
get_media_buy_delivery - Optimize: Use
provide_performance_feedback - Update: Use
update_media_buyto modify campaign
Learn More
- Media Buy Lifecycle - Complete campaign workflow
- get_products - Discover inventory
- Targeting - Targeting strategies
- Pricing Models - Currency and pricing