§ 01
E-commerce intelligence
Track competitor product launches, prices, and reviews. Archive media URLs to your own CDN through the capture pipeline before the source links expire.
§ The Amazon hub
Amazon
scraper.
No proxy needed. 1 pre-built endpoint, parsed JSON in seconds.
1 endpoint·From $0.003 per call·Median under 2s
§ One call
Send a URL.
Get back JSON.
The shop page scraper takes one input: url. The response carries every public field Amazon exposes.
Request
cURL
curl https://api.hproxy.com/v1/scrape/amazon/shop/page/by/url \
-H "Authorization: Bearer $HPROXY_KEY" \
-H "Content-Type: application/json" \
-d '{"url":"https://www.amazon.com/shop/sydneydelrey"}'POST // 1 call · $0.0030 · <2s
§ Coverage
What you can
actually pull.
§ 01
Shops
Shop and storefront pages with the product catalog and seller details.
§ Every endpoint
The full list.
Prices included.
Every line is a live endpoint. Click through for the input schema, response shape, and the curl recipe.
§ What people build
One Amazon scraper.
Many shapes of work.
§ 02
AI training data
Feed clean, structured Amazon JSON straight into your model fine-tuning pipeline. Same schema every call — no scraping infrastructure to maintain.
§ 03
Dashboards & reporting
Wire Amazon signals into internal dashboards. One API key, predictable JSON, dollar-denominated pricing — finance can reason about the bill.
§ Questions
The honest
answers.
The questions that come up before the first call. If yours isn’t here, the founder reads support email himself — just write in.
Do I need proxies to use the Amazon scraper?
No. Every endpoint runs on our residential pool — fifty million IPs sourced through opt-in partner SDKs. You send an HTTP request with your API key; rotation, retries, and anti-bot handling are ours to worry about.
How does HProxy get past Amazon’s rate limits and bot detection?
Each call is routed through a residential session that matches typical organic traffic patterns. We don’t advertise specifics; what matters is the result — a 99%+ success rate on public-data endpoints in real customer traffic.
What does the JSON response look like?
Every endpoint returns a flat top-level wrapper (platform, scraper, data, creditsUsed, elapsedMs, requestId) with the parsed Amazon entity inside data. See the live example near the top of this page for the exact shape.
Is scraping public Amazon data legal?
Public data scraping (no login, no private content, no PII beyond what amazon.com itself publishes) sits within the boundaries set by hiQ Labs v. LinkedIn and similar US/EU precedents. We don’t serve endpoints that touch authenticated content. You’re responsible for your own use of the data under your local data-protection law (GDPR, CCPA, etc.).
What does each call cost?
From $0.003 per call on the standard endpoints. Endpoints that do heavier upstream work — AI transcripts, posts with media archived to R2 — cost more. The exact per-call price shows on each endpoint row below. One call = one charge, never multiplied by record count.
Can I test before signing up?
Yes — the wallet starts with a $2 deposit that’s refundable for 24 hours. That’s plenty of calls to verify the response shape matches what you’re building across all 1 Amazon endpoints.
How fast are the responses?
Median response time across the Amazon endpoints is under 2 seconds. Heavier endpoints (deep comment threads, cursor-paginated lists) can run 4-8 seconds depending on the page depth requested.
§ Try it
Two dollars,
first run.
Sign in with Google, drop $2 in the wallet, fire your first Amazon call against amazon.com. If it doesn’t do what you need, the balance is refundable for 24 hours.