Amazon Keyword Suggestions - Autocomplete Keyword Research
Pricing
from $1.00 / 1,000 results
Amazon Keyword Suggestions - Autocomplete Keyword Research
Pull Amazon's own search autocomplete suggestions for any seed keyword, expanded a-z, across 18 marketplaces. The keywords Amazon shows shoppers - what they actually type - for listing optimisation and PPC research. HTTP-only, no account.
Pricing
from $1.00 / 1,000 results
Rating
0.0
(0)
Developer
Farhan Febrian Nauval
Maintained by CommunityActor stats
0
Bookmarked
3
Total users
2
Monthly active users
3 days ago
Last modified
Categories
Share
Amazon Keyword Suggestions — Autocomplete Keyword Research
Pull Amazon's own search autocomplete suggestions for any seed keyword, expanded a–z, across 18 marketplaces. These are the phrases Amazon shows shoppers — what people actually type — which is what you want for listing optimisation and PPC research. HTTP-only, no account, no API key.
Input
| Field | Type | Default | Description |
|---|---|---|---|
keywords | array | required | Seed terms to expand |
marketplace | enum | US | Which Amazon site — 18 supported |
department | string | aps | Search alias: aps (all), electronics, kitchen, books… |
expansion | enum | alphabet | none, alphabet (a–z), alphanumeric (a–z, 0–9) |
maxKeywordsPerSeed | integer | 500 | Stop a seed at this many unique keywords |
maxConcurrency | integer | 5 | Parallel requests |
Why the a–z expansion matters
A plain autocomplete call returns about 10 suggestions. Asking for the seed plus each
letter — laptop stand a, laptop stand b, … — turns that into a real keyword set:
| Seed | Probes | Unique keywords |
|---|---|---|
laptop stand | 27 | 243 |
yoga mat | 27 | 251 |
Keywords are deduplicated across probes (laptop b and laptop ba both surface laptop bag),
and each row keeps the prefix that produced it so you can see which probe found what.
Output
{"_input": "laptop stand","_source": "S1-completion-api","_scrapedAt": "2026-09-07T06:23:20Z","seed": "laptop stand","prefix": "laptop stand b", // the exact probe sent"keyword": "laptop stand bamboo","rank": 2, // position within that probe's answer"marketplace": "US","department": "aps","suggestionType": "KeywordSuggestion","strategyId": "organic","candidateSources": "local","isGhost": false,"refTag": "nb_sb_ss_i_1_6"}
494 rows across two seeds in testing, zero duplicates, every field populated.
How it works
completion.amazon.<tld>/api/2017/suggestions is the endpoint behind the search box.
Each marketplace has its own host — and the wrong one fails silently
This is the trap worth knowing. completion.amazon.com with a non-US marketplace id returns
HTTP 200 with an empty suggestions array. Not an error, not a redirect — just nothing. An
actor that hardcodes the .com host and swaps only the marketplace id therefore ships UK, DE and
JP options that quietly return no keywords, and nothing in the response says so.
Every host/id pair here was verified by asking for "laptop" and checking the answers came back in the right language:
| Market | Returns |
|---|---|
| DE | laptop ständer, laptoptasche, laptop 17 zoll |
| TR | laptop çantası |
| MX | laptop gamer |
| PL | laptop 17 cali |
17 of 18 marketplaces answered on the first attempt. India returned HTTP 502 during testing — it is included, but may fail.
Known limits
| Limit | Detail |
|---|---|
| No search volume | Amazon does not expose volume or competition here — these are suggestions, ranked, nothing more |
| ~10 per probe | The expansion is what produces breadth; there is no page parameter |
| Suggestions are personalised-ish | Ranking varies slightly by region and over time; run scheduled if you want a trend |
| India | 502 at the time of writing |