Documentation

Amazon Data API documentation

A JSON API over the surfaces the Amazon Shopping app uses. Everything is a plain GET with a query string and one header — no SDK required, no browser automation, no HTML parsing on your side.

Base URL
https://amazoncrawler.com/v1

How a request is shaped

Every endpoint takes its inputs as query parameters and returns a JSON object. There are no request bodies, no nested envelopes and no pagination cursors to decode — just page and, where supported, limit.

A complete request
curl -sS "https://amazoncrawler.com/v1/products/details?asin=B07CMS5Q6P&marketplace=US&zip=10001" \
  -H "x-api-key: ac_live_your_key_here"

Conventions worth knowing

Send a postcode

Amazon localises almost everything. Without a zip, many listings report “cannot be shipped to your location” and come back with no price and no images. Passing a delivery postcode is the single biggest quality lever in this API — treat it as effectively required for any price-sensitive workload.

Prices are objects, not strings

Anywhere a price appears you get both the display string and the parsed number, so you never have to strip currency symbols or guess at a locale's decimal separator.

price
{
  "display": "$29.99",
  "amount": 29.99,
  "currency": "USD",
  "list_price": 49.99
}

Gated surfaces return a note, not a lie

A few Amazon surfaces are client-rendered or hidden behind encrypted lazy-load calls — influencer post feeds and certain review blocks in particular. Rather than fail silently or fabricate data, those endpoints return whatever was genuinely extractable plus a note field explaining the limitation. Check for it before assuming an empty array means “no results”.

Endpoints that can return a note are flagged individually in the API Reference. It is worth reading the note field in your error handling rather than treating count: 0 as authoritative.

Every response carries diagnostics

HeaderMeaning
X-CacheHIT or MISS — whether the upstream fetch was served from cache.
X-Response-Time-MsServer-side processing time in milliseconds.
X-Credits-CostCredits this request consumed.
X-Credits-RemainingCredits left in the current billing period.
X-Credits-ResetISO-8601 timestamp when your quota resets.
X-RateLimit-LimitYour plan's per-second ceiling.

The endpoint surface

16 endpoints across five domains:

Where to go next