Skip to content

Amazon Prices by ZIP Code, on Demand

Amazon does not show one price for a product.

OUTPUT FORMATSHTMLJSONMarkdown

The figure a shopper sees depends on where the request appears to originate: the ZIP code behind the IP address can change the displayed price, the shipping charge, and whether Prime applies. This API takes an Amazon product URL plus a target ZIP, runs the page in a real headless browser, and returns the localized result so you can compare locations programmatically instead of manually switching addresses.

What the API returns for an ASIN-plus-ZIP pair

For each product URL and ZIP you submit, the response can carry the price shown to that location, the shipping cost, the delivery window, whether the item is Prime-eligible, and the seller. That combination is what makes regional variance visible: the same ASIN can present different numbers in two ZIPs, and Amazon does not publish that comparison in aggregate. The API does not invent a national price; it reports what the page renders for the location you asked for.

Three workflows this data supports

First, region-specific pricing: pull the displayed price, shipping cost and Prime eligibility for any ASIN across the ZIPs you track. Second, shipping cost comparison: line up delivery charges across locations to inform logistics and competitor pricing reviews. Third, ASIN collection: gather product ASINs from Amazon pages to feed competitive tracking and inventory analysis. Each workflow uses the same request shape; the difference is which fields you extract and how often you run it.

From URL to structured data: the request in four steps

Step 1: create an account to receive an API key and starting credits. Step 2: install a client SDK for Python, Node, Go, PHP or Ruby, or call the endpoint directly. Step 3: send the Amazon product URL to the API; the renderer geolocates the request, executes the page's JavaScript, and returns rendered HTML by default. Step 4: add parameters when the default is not enough — render_js for JavaScript execution, stealth_proxy for aggressive anti-bot responses, country_code to route through a residential IP in a specific country, and extract_rules or ai_extract_rules to receive parsed JSON instead of HTML.

Field and control map

Use this map to decide which request parameter and which output field you need before writing code.

Worked example: one ASIN, two ZIPs

Suppose you track a single ASIN and want to know whether a buyer in one ZIP sees a different total than a buyer in another. You send the same product URL twice, once with each target ZIP, and request parsed JSON via extract_rules with fields mapped to price, shipping cost, delivery window, Prime eligibility and seller. The two responses are then compared field by field. If the price matches but the shipping cost and delivery window differ, the variance is in fulfillment rather than the item price — a distinction that matters when you are evaluating logistics rather than competitor pricing. If one request returns a block page instead of product data, that is an anti-bot response, not a pricing result; retry with stealth_proxy enabled before treating the row as missing.

Telling the three failure modes apart

A blocked response means the target refused the request; enable stealth_proxy and retry. A throttled response means you are sending patterns faster than the target tolerates; the API itself enforces concurrency limits per plan rather than per-target rate limits, so space requests out or use multiple sessions. A missing field means the page rendered but the selector did not match; check your extract_rules mapping or switch to ai_extract_rules with a natural-language spec. Conflating these three leads to wasted credits and false conclusions about regional pricing.

If you do not want to write code

The dashboard includes a request builder: paste the URL, set parameters, and copy the generated snippet in Python, Node, Go, PHP, Ruby or cURL. You can test a request and inspect the response before committing to an integration. Code samples exist for each of those languages, and the documentation covers the parameter set.

Plans, credits and concurrency

Plans differ by monthly API credits, concurrent requests, and which support and team features are included. Credits are valid for one month and do not roll over; requests start at one credit each. Enabling JavaScript rendering costs five credits per successful request. Premium proxies cost ten or twenty-five credits per successful request depending on whether JavaScript rendering is also enabled. Geotargeting reaches 200+ countries and territories on premium proxies and 40+ on classic proxies. The plan comparison table below lists every tier with its exact credit and concurrency figures; treat those numbers as the reference for budgeting rather than estimating from the per-request costs alone.

How blocking and scaling are handled

Requests rotate residential proxies and run in a real headless browser, so traffic resembles ordinary browsing. When a target responds aggressively, stealth_proxy can be enabled per request. The platform is built to scale across many headless browsers and rotating proxies, and typical responses arrive within a few seconds even on JavaScript-heavy pages. These are the platform's stated operating characteristics; measure them against your own targets before relying on them for production SLAs.

Data handling and compliance posture

The platform states that it does not collect or store personal data from scraped sites unless the user explicitly requests it, and positions itself as GDPR and CCPA compliant. Scraping Amazon is subject to Amazon's own terms and to applicable law in your jurisdiction; confirm your use case against both before running at scale.

Request parameter to output field map
NeedRequest parameterOutput fieldNotes
JavaScript-rendered pagerender_js=truePost-render HTMLPage runs in a real headless browser; JS executes server-side.
Bypass aggressive anti-botstealth_proxyRendered pageEnable per request when the default response is a block page.
Route through a specific countrycountry_codeGeo-localized pageRoutes through a residential IP in that country.
Parsed JSON via selectorsextract_rulesJSON keyed by your field namesCSS selectors mapped to field names.
Parsed JSON via natural languageai_extract_rulesParsed JSONNatural-language spec instead of selectors.
Localized price(target ZIP + product URL)Displayed pricePrice shown to that ZIP.
Shipping cost(target ZIP + product URL)Shipping costDelivery charge for that location.
Delivery window(target ZIP + product URL)Delivery windowEstimated delivery range.
Prime eligibility(target ZIP + product URL)Prime eligibilityWhether Prime applies for that location.
Seller(target ZIP + product URL)SellerSeller shown for that location.

Parameters and fields reflect the documented request surface; exact selector names and response key names depend on your extract_rules mapping.

Frequently asked questions

Will I get blocked when scraping Amazon zip-code data?

Requests rotate residential proxies and run in a real headless browser, so they resemble normal traffic. If a target responds aggressively, enable stealth_proxy on the request.

Can I scrape Amazon zip-code data 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 zip-code data?

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

Can I scrape Amazon zip-code data from a specific country?

Yes. Pass country_code to route through a residential IP in that country. This is useful when content varies by geography.

What's the rate limit for scraping Amazon zip-code data?

The API enforces concurrency limits per plan rather than per-target rate limits. If a target throttles aggressive patterns, space requests out or use multiple sessions.

How do I get structured JSON from Amazon zip-code data?

You have two routes. With extract_rules, you supply CSS selectors and map each one to the field name you want in the output. With ai_extract_rules, you describe the fields you want in plain language instead of writing selectors. Either way, the API returns the result as parsed JSON rather than raw HTML.

How many credits does a single Amazon ZIP lookup cost?

Base requests start at one credit. Enabling JavaScript rendering costs five credits per successful request. Premium proxies cost ten or twenty-five credits per successful request depending on whether JavaScript rendering is also enabled. Credits are valid for one month and do not roll over.