Skip to content

Capture Amazon Spell Check Suggestions Programmatically

Amazon's spell-check layer exposes how the search engine corrects misspelled queries.

OUTPUT FORMATSHTMLJSONMarkdown

Instead of maintaining your own headless browser fleet and proxy rotation, you can send a misspelled query URL to a managed API and receive the suggested correction, alternate suggestions, and any product results served for the corrected term. This page explains the inputs, the options that change what comes back, and the credit costs so you can decide whether the managed route fits your workflow.

What the API returns

When you send a misspelled query URL, the API returns three things: the suggested correction Amazon would apply, the list of alternate suggestions, and any product results that Amazon serves for the corrected term. Three patterns come up most often when teams pull Amazon spell-check results. First, extracting product descriptions: the corrected term leads to listings whose copy you can compare against competitors and use for positioning decisions. Second, catching spelling errors in listings: spotting and correcting misspellings in product copy improves data accuracy and brand credibility. Third, extracting product ratings: the results served for the corrected term carry rating data you can use for competitor analysis and market positioning.

The underlying page runs on JavaScript with active bot detection. The managed layer handles both the rendering and the proxy rotation, so your client-side code stays a thin HTTP call rather than a browser automation project.

Beyond the correction data itself, the same API surface covers several adjacent capabilities: AI data extraction that turns a natural-language spec into structured output, full-page screenshots for visual records of results, Google search extraction for spell-check context, JavaScript scenarios that click and scroll before capture, Markdown output that is ready for LLM pipelines, and no-code automation through n8n workflows.

When to use a managed API for this

Use this checklist to decide whether the managed route fits your task:

  • You need the correction and alternate suggestions, not a full crawl of Amazon.
  • You want to avoid maintaining headless browsers and proxy pools.
  • You need to route requests through a specific country because results vary by geo.
  • You want the response as parsed JSON rather than raw HTML.
  • You are comfortable with per-plan concurrency limits rather than per-target rate limits.

If you need to scrape full product pages, reviews, or pricing at scale, a broader Amazon scraper is a better fit than this spell-check-specific endpoint.

Input, options, and output

The request flow has one input and several optional controls that change what comes back and what it costs.

Input: a misspelled query URL.

Options that affect the response:

  • render_js — executes the page in a real browser when JavaScript is needed.
  • stealth_proxy — routes through a stealth proxy for pages that present CAPTCHAs.
  • country_code — routes through a residential IP in the specified country so geo-varying content is captured.
  • extract_rules — maps CSS selectors to field names so the response is parsed JSON.
  • ai_extract_rules — accepts a natural-language spec instead of CSS selectors.

Output: the suggested correction, the alternate-suggestion list, and any product results served for the corrected term, returned as parsed JSON when extraction rules are supplied.

A worked example

Suppose a user types a misspelled product query into your keyword tool. You send that misspelled query URL to the API with country_code set to the market you care about. The response tells you which correction Amazon applied, which alternate suggestions it offered, and which product results were served for the corrected term. Your tool can then store the correction alongside the original misspelling, so future searches for that typo resolve to the right results without a second round trip.

If you also pass extract_rules with CSS selectors mapped to field names, the same response arrives as parsed JSON rather than raw HTML, which removes a parsing step from your pipeline.

Concurrency limits vs. target throttling

These are two different failure modes and they need different responses.

Concurrency limits are per plan. If you exceed the number of simultaneous requests your plan allows, the API will reject or queue the extra requests. The fix is to upgrade the plan or to pace your requests.

Target throttling is Amazon's own rate limiting. If Amazon throttles aggressive patterns, the fix is to space out requests or to use multiple sessions. The API does not impose per-target rate limits, so a throttle you see is coming from the target, not from the API's concurrency ceiling.

Credit costs per request

Credit cost depends on which options you enable. The table below summarizes the captured credit costs; treat them as a dated reference and check current pricing before committing to a plan.

Getting started

Setup takes a few minutes. Create an account to get an API key and free credits, install the SDK for your stack (Python, Node.js, Go, PHP, Ruby, or Java), and send the misspelled query URL with your API key. Plain cURL works too, and the dashboard includes a request builder for testing without writing code.

Code samples are available in Python, Node.js, Ruby, PHP, Go, and cURL. The documentation covers the full parameter set.

Credit cost per request by option
OptionCredits per request
Base request1
JavaScript rendering (render_js)5
Premium proxy without JS rendering10
Premium proxy with JS rendering25
Stealth proxy (stealth_proxy)75

Credit costs captured from the source page. Treat as a dated reference and check current pricing before committing.

Plan comparison (captured reference)
PlanPrice/moAPI 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. Captured reference; check current pricing before committing.

Frequently asked questions

Do I need an account to scrape Amazon Spell Check?

No external account is required. You sign up for an API key, which comes with free credits and no card requirement. After that you send the URL and the managed layer handles the rest.

Can I scrape Amazon Spell Check from a specific country?

Yes. Pass country_code on the request to route through a residential IP in that country. This is useful when the correction or the product results vary by geo.

What's the rate limit for scraping Amazon Spell Check?

The API applies concurrency limits per plan, not per-target rate limits. If the target throttles aggressive patterns, space out requests or use multiple sessions.

How do I get structured JSON from Amazon Spell Check?

You have two routes to parsed JSON. With extract_rules, you pair each CSS selector with the field name it should fill. With ai_extract_rules, you describe the fields you want in plain language instead of writing selectors. Either way, the response arrives already parsed rather than as raw HTML.

Which programming languages can I use to scrape Amazon Spell Check?

Any language works. SDKs are published for Python, Node.js, Go, PHP, Ruby, and Java, and plain cURL works too. Pick whatever your stack already uses.

How much does it cost to scrape Amazon Spell Check?

New accounts get free credits on signup with no card required. Paid plans start at $19/month for higher volume and concurrency. Credit cost per request depends on options: 5 credits for JS rendering, 25 for premium_proxy with JS, and 75 for stealth_proxy.