Skip to content

Collect Amazon Sponsored Brands Ad Placements With One API Call

Sponsored Brands placements change by keyword, by country and by day, which makes them awkward to track by hand.

OUTPUT FORMATSHTMLJSONMarkdown

A hosted scraping API lets you send a keyword page URL and receive the rendered page back, so your pipeline can pull the brand name, headline copy, carousel ASINs, lifestyle image and landing destination for each sponsored slot. This page explains what the API returns, which request parameters control rendering, proxies and geo, and how the credit model works so you can size a budget before you build.

What the API returns for a Sponsored Brands page

Each call targets a public Amazon keyword page. The API renders that page in a real headless browser, rotates the outbound IP and returns either the post-render HTML or a structured JSON payload. For Sponsored Brands slots you can expect to work with the brand name, the headline copy, the carousel ASINs, the lifestyle image URL, the slot position and the brand-store landing destination. The scope is whatever appears on the public page: define CSS or XPath extraction rules to target specific elements, or describe the fields you want in plain language and let AI-driven extraction rules return them as structured JSON.

Three workflows this data feeds

Most teams arrive with one of three jobs in mind. A creative library tracks every Sponsored Brands asset across a keyword set so messaging changes can be benchmarked over time. A share-of-voice view counts how often competitor brands appear in sponsored slots per query, alongside impression rank and ad-slot density. A competitive placement map records which brands bid on overlapping keywords, which is useful when planning your own sponsored campaigns. All three run on the same request shape; only the keyword list and the extraction rules differ.

Request parameter map

The parameters below are the ones that change what comes back. Start with the target URL and your API key, then add only the controls your keyword set actually needs.

How credits are consumed

Credits are valid for one month and do not roll over. A plain request starts at one credit. Enabling JavaScript rendering costs five credits per successful request. Premium proxies cost ten credits without JS rendering and twenty-five with it. That means a Sponsored Brands scrape that needs both rendering and premium proxies is a twenty-five-credit request, so a keyword list of a few thousand pages is a real budget line rather than a rounding error. Size the list against the plan's monthly credit allowance before scheduling a recurring job.

Telling three failures apart

A request that comes back empty or wrong is usually one of three things. If the response is a block or challenge page, the target is rejecting the traffic pattern and the fix is to enable stealth_proxy on the request. If the page returns but the sponsored slots are missing, the JavaScript has not finished executing and render_js=true is the setting to check. If the sponsored slots appear but belong to the wrong marketplace, the request is exiting from the wrong country and country_code needs to match the marketplace you are tracking. Each of these has a distinct parameter, so log the response status and the presence of the sponsored slot markup separately rather than treating every empty result as a block.

Worked example: one keyword, one creative

Suppose you track the keyword page for a category term and the response contains a Sponsored Brands carousel. The structured output would carry the brand name, the headline copy, the list of carousel ASINs, the lifestyle image URL, the slot position and the brand-store landing page. Store that row with the keyword and the capture timestamp. On the next run, compare the headline and the carousel ASINs against the stored row: a changed headline signals a creative refresh, and a changed ASIN set signals a product mix shift. Repeating this across a keyword list builds the creative library and the share-of-voice view from the same data.

Getting started

Create an account to receive an API key and a starter credit balance. Install the SDK for your stack, or skip the SDK and send a GET request with the target URL and your key. The dashboard includes a request builder that lets you paste a URL, set parameters and copy a generated snippet in Python, Node, Go, PHP, Ruby or cURL, which is useful for testing before you write production code. Code samples for each of those languages are available in the documentation.

Plan tiers and what they include

The plan table below lists the published tiers, their monthly credit allowances, concurrency limits and which features are bundled. Read it as a reference snapshot from the date shown, not as a live quote, and confirm current pricing before committing to a tier. All prices are exclusive of VAT. Every tier from Hobby upward includes JavaScript rendering, rotating and premium proxies, geotargeting and screenshots with extraction rules; the differences are credit volume, concurrency and whether priority support, a dedicated account manager and team management are included.

Data handling and compliance posture

The service does not collect or store personal data from scraped sites unless the user explicitly requests it. Proxy rotation and headless browser rendering are used to reduce IP-based blocking and to mimic ordinary browsing behaviour. Teams handling regulated data should still review the acceptable use policy and data processing agreement before pointing the API at any marketplace page.

Published plan tiers (reference snapshot)
PlanPrice / monthAPI creditsConcurrent requestsPriority email supportDedicated account managerTeam management
Hobby$1975,00025Not includedNot includedNot included
Freelance$49250,00050Not includedNot includedNot included
Startup (Recommended)$991,000,000100Not includedNot includedNot included
Business$2493,000,000200IncludedIncludedIncluded
Business +$5998,000,000400IncludedIncludedIncluded
Enterprise 14$99914,000,000500IncludedIncludedIncluded
Enterprise 24$1,59924,000,000600IncludedIncludedIncluded
Enterprise 41 (Recommended)$2,39941,000,000700IncludedIncludedIncluded
Enterprise 69$3,59969,000,000800IncludedIncludedIncluded
Enterprise 120$5,799120,000,000900IncludedIncludedIncluded

Prices are exclusive of VAT. Every tier includes JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots with extraction rules. Credits are valid for one month and do not roll over. This is a reference snapshot; confirm current pricing before purchase.

Frequently asked questions

What data can I extract from Amazon Sponsored Brands?

The public page sets the limit: whatever it displays can be captured. To shape the output, attach extract_rules built from CSS selectors, or hand the field descriptions to ai_extract_rules and let AI-driven extraction assemble them. Either route returns structured JSON you can store and query.

How do I get started scraping Amazon Sponsored Brands?

Sign up, copy your API key, and send a GET request with the target URL. The service renders the page, rotates proxies and returns the data. A starter credit balance is available for testing.

Will I get blocked when scraping Amazon Sponsored Brands?

Residential proxies are rotated and a real headless browser is used, so requests resemble ordinary traffic. If a target becomes aggressive, enable stealth_proxy on the request.

Can I scrape Amazon Sponsored Brands without writing code?

Yes. The dashboard request builder lets you paste a URL, set parameters and copy the generated snippet in Python, Node, Go, PHP, Ruby or cURL.

How do I handle JavaScript when scraping Amazon Sponsored Brands?

Pass render_js=true on the request. The page runs in a real headless browser, the JavaScript executes server-side, and the post-render HTML is returned.

Can I scrape Amazon Sponsored Brands from a specific country?

Yes. Pass country_code on the request to route through a residential IP in that country. This matters when sponsored content varies by geography.