Amazon Related Searches API: Turn Suggestion Pages Into Queryable Data
If you are mapping long-tail demand on Amazon, the related-query list under a seed search is one of the cheapest signals available.
This page covers a hosted endpoint that accepts an Amazon related-searches URL and returns the suggestion list, each suggestion's position, and any product carousels served alongside them. You supply the URL and your API key; the service handles rendering, proxy rotation and bot mitigation. The output can be raw HTML or structured JSON, depending on the extraction options you choose.
What this endpoint returns
The response is built around three data groups. First, the related-query suggestions that Amazon shows for the seed query. Second, the position of each suggestion in the list. Third, any product carousels that appear on the same page. That combination is what makes the data usable for keyword maps and intent analysis rather than a flat list of strings.
You can request parsed HTML when you want to inspect the page yourself, or structured JSON when you want to load the data directly into a pipeline. JSON output is produced either by mapping CSS selectors to field names with extract_rules, or by describing the fields you want in natural language with ai_extract_rules.
Three research patterns this data supports
Keyword mapping. Start from a set of seed queries and pull the related-query list for each one. The result is a long-tail map of phrases Amazon itself associates with your seeds, which you can use for SEO targeting or as PPC seed lists.
Listing and PPC suggestions. The same suggestion lists give you candidate phrases to test in titles, bullets and ad groups. Because the suggestions come from Amazon's own adjacency logic, they tend to reflect how shoppers phrase queries rather than how marketers phrase features.
Intent mapping. The suggestions that appear after an initial search show where shoppers tend to go next. Reading several seed queries together gives you a picture of intent paths, which is useful when refining product listings or deciding which adjacent categories to compete in.
Request controls and what each one changes
The endpoint accepts a target URL plus your API key. Beyond that, a small set of parameters controls how the page is fetched and what comes back.
- render_js turns on JavaScript rendering. It costs 5 API credits per successful request.
- stealth_proxy routes the request through stealth proxies. It costs 75 API credits per request.
- premium_proxy routes through premium proxies. It costs 10 credits without JS rendering, or 25 credits with JS rendering enabled.
- country_code sets the geotargeting country. Geotargeting reaches 200+ countries and territories, with 40+ available on classic proxies.
- extract_rules maps CSS selectors (or XPath) to field names so the response comes back as structured JSON.
- ai_extract_rules lets you describe the fields you want in natural language instead of writing selectors.
- screenshot captures a full-page image of the rendered page.
A practical rule: start with the cheapest configuration that returns the data you need, then add stealth_proxy only if you see blocks. JS rendering is usually required for Amazon related-searches pages because the suggestion list is rendered client-side.
A worked credit example
Suppose you have 50 seed queries and you want structured JSON for each one. You enable JS rendering and use extract_rules to map the suggestion text and position fields. Each successful request costs 5 credits, so 50 requests cost 250 credits. That fits comfortably inside the 75,000 credits on the entry-level plan, provided the batch runs within a single billing month: credits are valid for one month and do not roll over, so unused credits do not carry forward.
If you switch to stealth_proxy for the same 50 seeds, each request costs 75 credits, so the batch costs 3,750 credits. That is still within the entry-level allowance for a single month, but it is 15 times the cost of the plain JS-rendering run. The same non-rollover rule applies, so plan the batch to finish inside the month. The lesson is to test a small sample first and only escalate to stealth proxies for the seeds that actually get blocked.
Blocked request vs. empty suggestion list
These two failures look similar in a dashboard but mean different things. A blocked request usually returns a CAPTCHA page, a 403, or an Amazon error page instead of the related-searches layout. The fix is to add stealth_proxy, adjust country_code, or retry with a different proxy pool.
An empty suggestion list means the request succeeded but Amazon returned no related queries for that seed. That can happen with very narrow or branded seeds. The fix is not a proxy change; it is a seed change. Log the seed alongside the response so you can tell the two cases apart later, and treat an empty list as a valid result rather than a failure.
Getting started
Create an account to receive an API key and 1,000 free credits; no card is required for the trial. Install the SDK for your stack (Python, Node.js, Go, PHP, Ruby or Java), or call the endpoint with plain cURL. Test the request in the dashboard request builder first, then copy the generated snippet into your codebase.
The endpoint accepts any Amazon related-searches URL. You do not need to manage headless browsers or rotate proxies yourself; the service handles rendering and bot mitigation on its side. If you need more credits or concurrency than the standard plans offer, the enterprise tiers scale up to 120,000,000 credits and 900 concurrent requests per month.
| Configuration | Credits per successful request |
|---|---|
| JS rendering only | 5 |
| Premium proxy, no JS rendering | 10 |
| Premium proxy with JS rendering | 25 |
| Stealth proxy | 75 |
Credit costs are per successful request and depend on which options are enabled. Credits are valid for one month and do not roll over, so budget each batch to finish inside the billing month. Prices and plan allowances are subject to change; check the current pricing page before committing to a volume.
| Plan | Monthly price | API credits | Concurrent requests |
|---|---|---|---|
| Hobby | $19 | 75,000 | 25 |
| Freelance | $49 | 250,000 | 50 |
| Startup | $99 | 1,000,000 | 100 |
| Business | $249 | 3,000,000 | 200 |
| Business + | $599 | 8,000,000 | 400 |
| Enterprise 14 | $999 | 14,000,000 | 500 |
| Enterprise 24 | $1,599 | 24,000,000 | 600 |
| Enterprise 41 | $2,399 | 41,000,000 | 700 |
| Enterprise 69 | $3,599 | 69,000,000 | 800 |
| Enterprise 120 | $5,799 | 120,000,000 | 900 |
Prices and allowances shown are a captured reference and exclude VAT. Credits are valid for one month and do not roll over. Verify current plans and credit validity on the pricing page before purchase.
Frequently asked questions
Do I need an account to scrape Amazon related searches?
You do not need an Amazon account. You do need an API key from the service: sign up, receive 1,000 free credits without a card, and send the URL. The service handles the rest.
Is scraping Amazon related searches legal?
Public-facing pages are generally treated as scrapable, but you should review Amazon's terms of service before deploying and avoid any content behind a login. Legal treatment varies by jurisdiction and by how the data is used.
What data can I extract from Amazon related searches?
Anything that renders on the public page. In practice that means the related-query suggestions, their positions, and any product carousels shown alongside them. Use extract_rules with CSS selectors, or ai_extract_rules for AI-driven extraction, to get structured JSON back.
How do I get structured JSON from Amazon related searches?
Pass extract_rules with CSS selectors mapped to field names, or use ai_extract_rules with a natural-language specification. The response comes back as parsed JSON.
Which programming languages can I use to scrape Amazon related searches?
Any language that can make an HTTP request. SDKs are published for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works as well.
How much does it cost to scrape Amazon related searches?
There are 1,000 free credits on signup with no card required. Paid plans start at $19 per month for higher volume and concurrency. Per-request credit cost depends on the options: 5 credits for JS rendering, 25 for premium_proxy with JS, and 75 for stealth_proxy. Credits are valid for one month and do not roll over.