Amazon Keyword Scraper API
Last updated: · REST · JSON
Send GET https://proxy.scrapier.io/api/v2/amazon-keyword-suggestion/?queries=iphone with your key in the X-API-Key header. You get the keyword lookup back as JSON. 1 credit per keyword lookup; failed calls are free.
- 1 credit per keyword lookup
- Failed calls free
- 3 parallel requests per key
Call the Amazon Keyword Scraper API
Use the Amazon Keyword Scraper API from your own apps, scripts or agents. You need a Scrapier account and the API key from your dashboard. Pick a language.
import requests# Replace YOUR_API_KEY with the key from your Scrapier dashboardAPI_KEY = "YOUR_API_KEY"params = { "queries": "iphone", "max_items": "50",}r = requests.get( "https://proxy.scrapier.io/api/v2/amazon-keyword-suggestion/", headers={"X-API-Key": API_KEY}, params=params, timeout=210,)r.raise_for_status()# The result sits under data.resultresult = r.json()["data"]["result"]print(result)
// Replace YOUR_API_KEY with the key from your Scrapier dashboardconst API_KEY = "YOUR_API_KEY";const params = new URLSearchParams({ queries: "iphone", max_items: "50",});const res = await fetch(`https://proxy.scrapier.io/api/v2/amazon-keyword-suggestion/?${params}`, { headers: { "X-API-Key": API_KEY }, signal: AbortSignal.timeout(210_000),});if (!res.ok) throw new Error(`HTTP ${res.status}`);const { data } = await res.json();console.log(data.result);
# One GET request. The key goes in a header, never in the URL.GET /api/v2/amazon-keyword-suggestion/?queries=iphone&max_items=50 HTTP/1.1Host: proxy.scrapier.ioX-API-Key: YOUR_API_KEYAccept: application/json
# Scrapier publishes an OpenAPI spec that covers every endpoint. No API key needed.curl -O https://proxy.scrapier.io/api/v2/openapi.json# Import openapi.json into Postman, Insomnia, Bruno or a code generator,# then add your key as the X-API-Key header.
# 1. Add the Scrapier MCP server to Claude Codeclaude mcp add -t http scrapier https://mcp.scrapier.io/mcp --header "X-API-Key: YOUR_API_KEY"# 2. Ask your agent. It finds the endpoint with search_endpoints# and calls it with run_scrape:"Get Amazon's search suggestions for laptop and list them"run_scrape("amazon-keyword-suggestion", {queries: "iphone"})
Amazon Keyword Scraper API in Python
Plain requests is all you need — no SDK. Every response is typed JSON.
Install
Amazon Keyword Scraper API in JavaScript
Works in Node 18+, Deno, Bun and edge runtimes with the built-in fetch.
Check your setup
Amazon Keyword Scraper API over HTTP
One GET request. Auth is a single X-API-Key header.
Check your setup
Amazon Keyword Scraper API OpenAPI definition
Download the spec once, then import it into the tools you already use. No key is needed to fetch it.
Download the spec
Amazon Keyword Scraper API over MCP
The same endpoint is a tool call for Claude Code, Cursor and Windsurf. Same queries, same 1 credit per keyword lookup.
Install
Other ways to call it
Amazon Keyword Scraper API Interactive Playground
Edit the request, watch the code update, then run it. Without a key it shows the catalog sample and bills nothing. With your key it makes a real call from your browser; the key goes only to proxy.scrapier.io and is never stored.
GET /api/v2/amazon-keyword-suggestion/?queries=iphonePress Run request to send it. Without a key you get the catalog sample.
Failed calls are not billed.
The sample is the same for every input: it shows the response shape, not the account you typed.
Example response, catalog sample from 9 Nov 2026
{
"success": true,
"data": {
"queries": "laptop",
"result": {
"query": "laptop",
"success": true,
"suggestions": [
{
"keyword": "laptop",
"type": "suggestion",
"item": "laptop"
},
{
"keyword": "laptop",
"type": "suggestion",
"item": "laptop stand"
},
{
"keyword": "laptop",
"type": "suggestion",
"item": "laptop cooling pad"
}
]
},
"next_cursor": null
}
}Data You Can Extract
Amazon Keyword Scraper takes a seed keyword and returns the search suggestions Amazon's search box offers for it. Every field below comes from the catalog sample response, as typed JSON.
Lookup
3 fields in the response.
- query
- success
- suggestions
Response envelope
3 fields in the response.
- success
- data.queries
- data.next_cursor
Response Schema Reference
Every field in the sample response. Field names stay the same on every call.
| Field | Type | Example | Description |
|---|---|---|---|
result.query | string | "laptop" | The seed keyword you sent |
result.success | boolean | true | true when the lookup worked |
result.suggestions | array | 3 items | List of suggestions, each with keyword, type and item |
success | boolean | true | true on every 200 response |
data.queries | string | "laptop" | Your input, echoed back |
data.next_cursor | null | null | Always null: this is a single lookup |
Request Parameters Reference
| Name | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
queries | string | Yes | — | The seed keyword, one per call. Required. Aliases: keyword, keywords, query | iphone |
max_items | integer | No | 50 | Maximum items to return, default 50 | 50 |
use_proxy | boolean | No | true | Route through Scrapier's residential proxy pool, on by default. Leave as is | true |
raw_data | boolean | No | false | Return Amazon's raw upstream payloads under raw_responses instead of the formatted items | true |
One keyword per call: to expand ten seeds, make ten calls. Booleans are the strings true or false.
Pagination in the Amazon Keyword Scraper API
The Amazon Keyword Scraper API is a single lookup: one call returns the whole result and there is no cursor to page through. A successful call costs 1 credit; failed calls cost 0.
Access Without Amazon Login
The Amazon Keyword Scraper API needs no Amazon account, no login and no session cookies. You send your Scrapier key in the X-API-Key header and get JSON back. It reads public data only: what any visitor sees without logging in.
Speed, Cost and Concurrency
| Metric | Value | Source |
|---|---|---|
| Cost of a successful call | 1 credit | Scrapier catalog |
| Cost of a failed call | 0 credits | Any non-2xx response |
| Parallel requests per key | 3 | Above that: 429 with Retry-After |
| Recommended client timeout | 210 seconds | Scrapier docs, every endpoint |
Latency of the Amazon Keyword Scraper API
Scrapier does not publish a latency or success-rate figure for this endpoint. Each call reads Amazon at call time, so response time depends on Amazon and on the size of the result. Set a client timeout of 210 seconds, as the docs recommend for every endpoint.
Limits of the Endpoint
Honest constraints of the Amazon Keyword Scraper API.
- Public data only.
- A failed call, for example a missing or unavailable keyword lookup, returns a non-2xx status and costs 0 credits.
- Data is read live at call time.
- 3 parallel requests per key; above that the API answers
429withRetry-After. - Fields Amazon does not show are not returned.
Scrapier vs the Official Amazon API
If you need search volumes or rank data, this endpoint does not return them; it returns suggestion text. If you run your own scraping stack, DIY gives more control.
| Feature | Scrapier Amazon Keyword Scraper | DIY Amazon scraping |
|---|---|---|
| Access needed | One Scrapier API key | Your own proxies, parser and servers |
| Which data | Suggestions Amazon offers for a seed keyword | Whatever your parser extracts |
| Fields returned | 3 fields per lookup: the seed, a status and the list of suggestions | Whatever you build and maintain |
| Setup | Sign up, copy a key, send a request | Write requests, handle blocks and retries |
| Cost | 1 credit per lookup, from $1.20 per 1,000 calls | Proxy, server and engineering time |
Errors and Retry Handling
| Status | Meaning | Billed | Fix |
|---|---|---|---|
| 200 | Keyword lookup data returned in data.result | Yes | — |
| 400 | Bad or missing input | No | Check queries: one value per call |
| 401 | X-API-Key header missing | No | Add the header |
| 402 | Out of credits (body has balance) | No | Top up; retrying will not help |
| 403 | Invalid or revoked API key | No | Check the key in your dashboard |
| 429 | Throttled | No | Wait Retry-After seconds, then retry |
| 5xx | Upstream failure or timeout | No | Retry with backoff; set a 210 s client timeout |
From the error reference. Any non-2xx response costs 0 credits.
Retry logic for the Amazon Keyword Scraper API
import time, requests def get_keyword_suggestion(value, key, tries=5): for attempt in range(tries): r = requests.get( "https://proxy.scrapier.io/api/v2/amazon-keyword-suggestion/", headers={"X-API-Key": key}, params={"queries": value}, timeout=210, ) if r.status_code == 429: time.sleep(int(r.headers.get("Retry-After", 2 ** attempt))) elif r.status_code >= 500: time.sleep(2 ** attempt) else: r.raise_for_status() return r.json() raise RuntimeError("gave up after retries")
Pricing and Rate Limits
| Plan | Monthly price | Keyword Lookups included | Cost per 1,000 |
|---|---|---|---|
| Hobby | $29 | 15,000 | $1.93 |
| Pro | $79 | 50,000 | $1.58 |
| Scale | $299 | 250,000 | $1.20 |
Billing rules for the Amazon Keyword Scraper API
The Amazon Keyword Scraper API bills 1 credit per successful keyword lookup. Failed calls, meaning any non-2xx status, cost 0 credits. Every plan allows 3 parallel requests per key. The free tier lets you try it before you pay.
Bulk Lookups and CSV
queries takes one value per call. For a list, loop and run up to 3 requests in parallel per key, then flatten each row into one CSV line.
import csv, requests from concurrent.futures import ThreadPoolExecutor values = ["iphone"] # your list def fetch(value): r = requests.get( "https://proxy.scrapier.io/api/v2/amazon-keyword-suggestion/", headers={"X-API-Key": "YOUR_API_KEY"}, params={"queries": value}, timeout=210, ) r.raise_for_status() out = r.json()["data"]["result"] return out if isinstance(out, list) else [out] # 3 parallel requests per key is the limit with ThreadPoolExecutor(max_workers=3) as pool: rows = [row for part in pool.map(fetch, values) for row in part] cols = ["query", "success"] with open("out.csv", "w", newline="") as f: w = csv.DictWriter(f, fieldnames=cols, extrasaction="ignore") w.writeheader() w.writerows(rows)
CSV export from the Amazon Keyword Scraper API
query,success laptop,true
AI Agent Access via MCP
MCP for the Amazon Keyword Scraper API
The same endpoint is available to AI agents through the Scrapier MCP server at https://mcp.scrapier.io/mcp. One command registers it in Claude Code: claude mcp add -t http scrapier https://mcp.scrapier.io/mcp --header "X-API-Key: YOUR_API_KEY". The agent finds the endpoint with search_endpoints and calls it with run_scrape and the endpoint id amazon-keyword-suggestion. It takes the same queries input and costs the same 1 credit per keyword lookup. Setup for every client is on the Amazon Keyword Scraper MCP page.
Integration Paths by Role
n8n and Make
- Add an HTTP Request step
- GET the endpoint with your
X-API-Keyheader - Map the
data.resultfields to your columns
Loop and paginate
MCP tool in your agent
Call run_scrape with endpoint amazon-keyword-suggestion from Claude, Cursor or Windsurf. Setup is on the MCP page.
CSV and flattened JSON
Flatten each row into one CSV line, one column per field, ready for Sheets, Excel or a BI tool.
Legal and Compliance Notes
Scraping publicly available web pages is generally lawful in many countries, but the answer depends on what you collect, where you are and how you use it. In the US, hiQ Labs v. LinkedIn is the case most often cited on public-data scraping. Scrapier returns only data any visitor can see without logging in. Search suggestions are search phrases, not personal data. Under GDPR and similar laws, collecting public data can be permissible, but how you store and use personal data must still comply with local data-protection rules, and Amazon's terms apply. Consult legal counsel if your use case involves bulk storage of personal data. This is not legal advice; see our Terms of Use.
Frequently Asked Questions
Is there a Amazon keyword lookup API?
Yes. Scrapier's Amazon Keyword Scraper API returns any public keyword lookup as JSON with one GET request and an X-API-Key header. No Amazon app or login.
How do I call it from Python?
Use <code>requests.get</code> on <code>https://proxy.scrapier.io/api/v2/amazon-keyword-suggestion/</code> with <code>params={'queries': 'iphone'}</code> and <code>headers={"X-API-Key": KEY}</code>. Read <code>r.json()["data"]["result"]</code>.
What happens when a call fails?
Any non-200 response is free. Retry 429 and 5xx with backoff; the API already retries upstream failures.
How much does it cost?
1 credit per successful call — about $1.58 per 1,000 keyword lookups on the Pro plan. Failed calls are free.
Is there an OpenAPI spec?
Yes. It needs no key and covers every Scrapier endpoint.
Related Amazon APIs
Search API
Search results for one keyword on 8 Amazon marketplaces: ASIN, price, rating, review count, Prime flag and sales volume.
amProduct API
Search results or one /dp/ product by keyword or URL: price, stars, reviews, bought past month and badges, in the marketplace you pick.
amBest Sellers API
Ranked Best Sellers for a category URL: position, ASIN, price, stars, review count and subcategories.
amAll Amazon APIs
All 8 Amazon endpoints.
Fetch public Amazon keyword lookups as typed JSON in one request
1 credit per keyword lookup · failed calls free