Create a Sponsored Products campaign via Amazon Ads API
domain: advertising.amazon.com/API/docs · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Complete the Amazon Ads API OAuth 2.0 flow and obtain an access token; include the Amazon-Advertising-API-ClientId and Amazon-Advertising-API-Scope (profile ID) headers on every request.
POST to https://advertising-api.amazon.com/v2/campaigns with a body containing name, campaignType (sponsoredProducts), targetingType (manual or auto), state (paused), dailyBudget, and startDate.
Capture the campaign id and create an Ad Group by POSTing to /v2/adGroups with campaignId, name, defaultBid, and state.
For manual targeting, create targeting clauses by POSTing to /v2/targets with adGroupId, expressionType (manual), and expression (keyword or product target).
Create ads by POSTing to /v2/productAds with adGroupId, campaignId, sku or asin, and state.
Verify creation with GET /v2/campaigns/{CAMPAIGN_ID} and check for any asynchronous validation errors in the mutationId response field.
Known gotchas
The Amazon-Advertising-API-Scope header must contain the advertiser profile ID (not the account ID) specific to the marketplace being targeted; each marketplace has a separate profile.
Sponsored Products campaigns require the advertised products to be in active, buyable listings; ads referencing suppressed or inactive ASINs will be paused by Amazon.
Daily budget minimums vary by marketplace and campaign type; budgets below the floor are rejected with a budget validation error.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?