Ecommerce Data API

Amazon Keyword Search Volume API

Get monthly Amazon search volume, purchases, product counts and suggested bids for any keyword in 13 marketplaces, as JSON you can filter and sort.
Sep 14, 2026

What this API returns

The Keyword Research endpoint answers the questions sellers ask before choosing a term for a listing or a campaign: how many people search for it on Amazon each month, how many of those searches end in a purchase, and how many products already compete for it.

Every result row is one keyword in one marketplace and one month. The fields most teams use first:

FieldWhat it tells youDocumented example
searchesEstimated monthly Amazon search volume for the keyword17702
purchasesEstimated purchases that followed those searches2436
purchaseRatepurchases ÷ searches, as a fraction0.1376
productsNumber of products competing for the keyword364623
supplyDemandRatiosearches ÷ products: demand per competing product0.05
searchMonthlyCv / searchMonthlyCrChange against the previous month, absolute and in percent-12649 / -41.68
bid, bidMin, bidMaxSuggested sponsored-products bid and its range1.26 (0.91–1.4)
avgPrice, avgRating, avgRatingsWhat the products ranking for the term look like17.97, 4.8, 25985

The example values come from the same response, so you can check the arithmetic yourself: 2436 ÷ 17702 = 0.1376, and 17702 ÷ 364623 rounds to 0.05. The full field list is in the Keyword Research reference.

See real responses

Saved responses captured from the live API on 2026-10-15, not live calls. Create a key to query any ASIN or keyword.

Run it on your own ASIN or keyword

POST/v1/amazon/keyword-research200 OK
Request
{
  "marketplace": "US",
  "keywords": "wireless charger",
  "month": "nearly",
  "page": 1,
  "size": 2
}
Response
{
  "request_id": "b118bd5d-f4e0-45f5-879d-60f74b07f76d",
  "data": {
    "total": 429,
    "pages": 215,
    "page": 1,
    "size": 2,
    "items": [
      {
        "keywords": "wireless charger",
        "month": "2026.09",
        "searches": 168369,
        "searchMonthlyCr": -11.3,
        "purchases": 8301,
        "purchaseRate": 0.0493,
        "products": 103802,
        "supplyDemandRatio": 1.62,
        "avgPrice": 13.24,
        "avgRatings": 10326,
        "bid": 1.44,
        "bidMin": 0.9,
        "bidMax": 1.8,
        "araClickRate": 0.3084,
        "brands": [
          "SMILE STATION",
          "TNDAJI",
          "Anker"
        ]
      },
      {
        "keywords": "charger wireless",
        "month": "2026.09",
        "searches": 2167,
        "searchMonthlyCr": -5.78,
        "purchases": 203,
        "purchaseRate": 0.0939,
        "products": 102128,
        "supplyDemandRatio": 0.02,
        "avgPrice": 9.48,
        "avgRatings": 3428,
        "bid": 1.93,
        "bidMin": 1.45,
        "bidMax": 2.41,
        "araClickRate": 0.2879,
        "brands": [
          "LMOYPD",
          "SMILE STATION",
          "TNDAJI"
        ]
      }
    ]
  }
}

Request example

curl --request POST \
  --url https://ecommercedataapi.com/v1/amazon/keyword-research \
  --header "Content-Type: application/json" \
  --header "X-API-Key: ${ECOMMERCE_DATA_API_KEY}" \
  --data '{
    "keywords": "wireless charger",
    "marketplace": "US",
    "month": "202507",
    "page": 1,
    "size": 20
  }'
  • marketplace is required. Supported codes: US, JP, UK, DE, FR, IT, ES, CA, IN, MX, BR, AU, AE.
  • month takes yyyyMM for a calendar month (up to 24 months back) or nearly for the latest 30 days.
  • The request body is validated strictly: send keywords (plural). Unknown fields are rejected rather than ignored.

Filter and sort by search volume

The endpoint is a query over a keyword database, not a single lookup. The same request can narrow results by range filters and sort them:

  • minSearches / maxSearches keep terms inside a search-volume band, for example long-tail terms between 1,000 and 10,000 searches a month.
  • minWordCount / maxWordCount separate head terms from long-tail phrases.
  • minPurchaseRate, minSupplyDemandRatio and maxProducts find terms where demand is high relative to competition.
  • excludeKeywords removes brand or irrelevant terms.
  • order.field sorts by searches, growth and other documented fields (Table 1.8).

Common workflows

  1. Size a niche before sourcing. Pull the terms around a seed keyword, sum searches for the ones that describe your product, and compare products to see how crowded it is. The product research workflow shows the full sequence.
  2. Build a keyword library. Combine this endpoint with the keyword miner and weekly search-term rankings, then deduplicate. See building a keyword library.
  3. Check seasonality. One month of searches hides peaks. The keyword research trends endpoint returns the monthly history for a term; seasonal product research explains how to read it.
  4. Set a starting bid. bid, bidMin and bidMax give a first reference for sponsored-products campaigns; keyword bidding covers how to adjust from there.

Limits worth knowing

  • searches, purchases and bids are estimates, not figures published by Amazon. Use them to compare terms and track direction; for your own brand, check them against the Search Query Performance report in Brand Analytics.
  • Different tools label different metrics as "search volume". Choosing a keyword tool explains why numbers disagree across tools.
  • Each successful call consumes one billing unit. Handle 429 responses as described in errors and rate limits.

FAQ

Is this the same data as the Amazon Ads API? No. The Amazon Ads API is for managing and reporting on your own campaigns. This endpoint returns marketplace-level estimates for any keyword, including terms you have never advertised on.

Which marketplaces are covered? The 13 marketplaces listed above. Pass the two-letter code in marketplace.

Can an AI agent call it? Yes. The same endpoint is exposed as a tool through the remote MCP server, so Claude Code, Cursor and other MCP clients can query keywords directly.