Amazon Keyword Search History

Track exact Amazon keyword search volume in seven-day periods across 10 marketplaces. Call via REST API or MCP from 88 credits per call.

CostRecent Avg. 132 · Range 67–133 credits / call

Try online

POST · https://api.nexscope.ai/js/keywords/historical-search-volumeMCP · nexscope_amazon_keyword_search_history

What this API does

Track exact Amazon keyword search volume in seven-day periods across 10 marketplaces. The request accepts marketplace, keyword, startDate, endDate. Its documented result includes historicalSearchVolumeList, id, estimateStartDate, estimateEndDate.

Amazon Keyword Search History API use cases

Build a keyword shortlist

To build a keyword shortlist, a marketplace analyst submits marketplace and keyword to Amazon Keyword Search History. The returned historicalSearchVolumeList, id, estimateStartDate help choose candidate search terms for further investigation.

Compare search demand signals

A marketplace analyst uses Amazon Keyword Search History with marketplace and keyword to compare search demand signals. The returned historicalSearchVolumeList, id, estimateStartDate help compare keyword demand within the requested market scope.

Plan a content or advertising test

For this workflow, a marketplace analyst calls Amazon Keyword Search History with marketplace and keyword to plan a content or advertising test. The result helps select terms for a content or advertising experiment.

Amazon Keyword Search History API FAQ

What does the Amazon Keyword Search History API return?

Track exact Amazon keyword search volume in seven-day periods across 10 marketplaces. The documented output includes historicalSearchVolumeList, id, estimateStartDate, estimateEndDate. It corresponds to the supplied marketplace, keyword, startDate, endDate. Optional fields can be absent; a missing value should not be interpreted as a measured zero. Example values illustrate the response shape, rather than live account results.

How many credits does the Amazon Keyword Search History API cost?

The current documented cost is Recent Avg. 132 · Range 67–133 credits / call. This is the same cost shown at the top of this page. If a range or estimate is displayed, the final charge depends on the request. Review your available credits and the pricing page before calling the API, and check API usage records for the actual charge.

How do I call the Amazon Keyword Search History API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/js/keywords/historical-search-volume with your API key as a Bearer token and the JSON inputs shown in API integration. In a compatible MCP client such as Claude or Cursor, connect Nexscope and call nexscope_amazon_keyword_search_history. Use the MCP arguments shown in the MCP guide, or switch Online test to MCP to review its request before adding it to your app.

View plans and credits Connect this API with MCP

Try this API

Endpoint

https://api.nexscope.ai/js/keywords/historical-search-volume

MCP method

nexscope_amazon_keyword_search_history

Step 1 of 3 · Authenticate

Authentication

All run endpoints require a user API key. Send it as a bearer token in the Authorization header.

Authorization: Bearer nk-xxxxxxxxxxxxxxxxx

Missing or invalid API keys return an authentication error. Manage keys from .

Step 2 of 3 · Send a request

POSThttps://api.nexscope.ai/js/keywords/historical-search-volume

Run an API

Send a JSON request body using the parameters described below.

Example request

Replace YOUR_API_KEY, then run this command in your terminal.

curl -X POST 'https://api.nexscope.ai/js/keywords/historical-search-volume' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "endDate": "2026-03-31",
  "keyword": "yoga mat",
  "marketplace": "us",
  "startDate": "2025-10-01"
}'

Code example

{
  "endDate": "2026-03-31",
  "keyword": "yoga mat",
  "marketplace": "us",
  "startDate": "2025-10-01"
}

Step 3 of 3 · Inspect the result

Check the response

Read code for the request status and data for the result. Open the parameter and response reference for the full field definitions.

HTTP status codes

Code	Description
200	Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result.
429	Execution admission rate limit; honor Retry-After when present.
503	Execution admission is temporarily unavailable; honor Retry-After when present.
Opt-in	X-Nexscope-Http-Status: semantic maps controller-handled business errors to HTTP status on run and task routes. Pre-authentication failures, such as a missing API key (code 11209), may still return HTTP 200 before this mapping. Always check the outer JSON code; malformed requests and infrastructure failures may also return non-200 HTTP responses.

View parameters & response Try online

All categories/ Amazon Research JS

POSThttps://api.nexscope.ai/js/keywords/historical-search-volume

Run this API

Send a JSON request to execute this API and receive the documented response payload.

Open tester

Endpoint

Method	`POST`
Path	`https://api.nexscope.ai/js/keywords/historical-search-volume`
Auth	`Bearer API key`
Content-Type	`application/json`

Request parameters

Name	Type	Required	Description
`marketplace`	`string`	required	Target market code. Optional values: `us`, `uk`, `de`, `in`, `ca`, `fr`, `it`, `es`, `mx`, `jp` Example: us
`keyword`	`string`	required	Keywords to be searched
`startDate`	`string`	required	Start date (format: YYYY-MM-DD)
`endDate`	`string`	required	End date (format: YYYY-MM-DD); maximum 366 days apart from `startDate`

Response example

Platform response envelope. code 0 indicates success or acceptance; data contains the business result.

No response example is published for this API. Refer to the response fields below.

Response fields

Response field reference (6 fields)

Name	Type	Required	Description
`costToken`	`integer`	optional	Number of tokens consumed
`historicalSearchVolumeList`	`array`	optional	List of historical search volume periods
`id`	`string`	optional	Data period identification (market/keyword/date range)
`estimateStartDate`	`string`	optional	Period start date (YYYY-MM-DD, starting point of the 7-day statistical period)
`estimateEndDate`	`string`	optional	Period end date (YYYY-MM-DD, end of 7-day statistical period)
`type`	`string`	optional	Resource type, fixed value `historical_keyword_search_volume`

Responses

Code	Description
200	Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result.
429	Execution admission rate limit; honor Retry-After when present.
503	Execution admission is temporarily unavailable; honor Retry-After when present.
Opt-in	X-Nexscope-Http-Status: semantic maps controller-handled business errors to HTTP status on run and task routes. Pre-authentication failures, such as a missing API key (code 11209), may still return HTTP 200 before this mapping. Always check the outer JSON code; malformed requests and infrastructure failures may also return non-200 HTTP responses.

Data source, freshness, and limitations

Source, freshness, coverage, rate limits, and estimation notes are not specified in this API definition unless they appear in the request or response field documentation above. Do not assume official marketplace data or real-time freshness when it is not explicitly documented.

Step 1 of 2 · Connect your MCP client

MCP

V2 recommended

Connect remote agents through the standard MCP 2025-11-25 Streamable HTTP endpoint. Use OAuth 2.1 Authorization Code with PKCE, or an API key for compatibility.

POST https://api.nexscope.ai/mcp
MCP-Protocol-Version: 2025-11-25
Content-Type: application/json

Authentication

OAuth clients request the mcp:tools scope. The endpoint's 401 response advertises protected-resource metadata for authorization discovery.

Step 2 of 2 · Call the tool

Call a tool

{
  "jsonrpc": "2.0",
  "id": "tool-call-1",
  "method": "tools/call",
  "params": {
    "name": "nexscope_amazon_keyword_search_history",
    "arguments": {
      "endDate": "2026-01-31",
      "keyword": "phone case",
      "marketplace": "us",
      "startDate": "2026-01-01"
    }
  }
}

Legacy MCP v1

Existing API-key clients can continue using the compatibility endpoint. New integrations should use MCP v2.

GET / POST /mcp/legacy

Data Example

Request parameters

{
  "marketplace": "fr",
  "keyword": "enigmes",
  "startDate": "2024-10-06",
  "endDate": "2025-10-04"
}

Response

{
  "code": 0,
  "msg": null,
  "data": {
    "costToken": 85000,
    "historicalSearchVolumeList": [
      {
        "id": "fr/enigmes/2024-11-03/2024-11-09",
        "estimateStartDate": "2024-11-03",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 79,
        "estimateEndDate": "2024-11-09"
      },
      {
        "id": "fr/enigmes/2024-11-10/2024-11-16",
        "estimateStartDate": "2024-11-10",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 110,
        "estimateEndDate": "2024-11-16"
      },
      {
        "id": "fr/enigmes/2024-11-17/2024-11-23",
        "estimateStartDate": "2024-11-17",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 100,
        "estimateEndDate": "2024-11-23"
      },
      {
        "id": "fr/enigmes/2024-11-24/2024-11-30",
        "estimateStartDate": "2024-11-24",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 213,
        "estimateEndDate": "2024-11-30"
      },
      {
        "id": "fr/enigmes/2024-12-01/2024-12-07",
        "estimateStartDate": "2024-12-01",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 254,
        "estimateEndDate": "2024-12-07"
      },
      {
        "id": "fr/enigmes/2024-12-08/2024-12-14",
        "estimateStartDate": "2024-12-08",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 287,
        "estimateEndDate": "2024-12-14"
      },
      {
        "id": "fr/enigmes/2024-12-15/2024-12-21",
        "estimateStartDate": "2024-12-15",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 368,
        "estimateEndDate": "2024-12-21"
      },
      {
        "id": "fr/enigmes/2024-12-22/2024-12-28",
        "estimateStartDate": "2024-12-22",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 106,
        "estimateEndDate": "2024-12-28"
      },
      {
        "id": "fr/enigmes/2024-12-29/2025-01-04",
        "estimateStartDate": "2024-12-29",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 105,
        "estimateEndDate": "2025-01-04"
      },
      {
        "id": "fr/enigmes/2025-01-05/2025-01-11",
        "estimateStartDate": "2025-01-05",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 105,
        "estimateEndDate": "2025-01-11"
      },
      {
        "id": "fr/enigmes/2025-01-12/2025-01-18",
        "estimateStartDate": "2025-01-12",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 105,
        "estimateEndDate": "2025-01-18"
      },
      {
        "id": "fr/enigmes/2025-01-19/2025-01-25",
        "estimateStartDate": "2025-01-19",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 105,
        "estimateEndDate": "2025-01-25"
      },
      {
        "id": "fr/enigmes/2025-01-26/2025-02-01",
        "estimateStartDate": "2025-01-26",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 105,
        "estimateEndDate": "2025-02-01"
      },
      {
        "id": "fr/enigmes/2025-02-02/2025-02-08",
        "estimateStartDate": "2025-02-02",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 105,
        "estimateEndDate": "2025-02-08"
      },
      {
        "id": "fr/enigmes/2025-02-09/2025-02-15",
        "estimateStartDate": "2025-02-09",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 105,
        "estimateEndDate": "2025-02-15"
      },
      {
        "id": "fr/enigmes/2025-02-16/2025-02-22",
        "estimateStartDate": "2025-02-16",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 105,
        "estimateEndDate": "2025-02-22"
      },
      {
        "id": "fr/enigmes/2025-02-23/2025-03-01",
        "estimateStartDate": "2025-02-23",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 105,
        "estimateEndDate": "2025-03-01"
      },
      {
        "id": "fr/enigmes/2025-03-02/2025-03-08",
        "estimateStartDate": "2025-03-02",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 105,
        "estimateEndDate": "2025-03-08"
      },
      {
        "id": "fr/enigmes/2025-03-09/2025-03-15",
        "estimateStartDate": "2025-03-09",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 105,
        "estimateEndDate": "2025-03-15"
      },
      {
        "id": "fr/enigmes/2025-03-16/2025-03-22",
        "estimateStartDate": "2025-03-16",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 105,
        "estimateEndDate": "2025-03-22"
      },
      {
        "id": "fr/enigmes/2025-03-23/2025-03-29",
        "estimateStartDate": "2025-03-23",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 105,
        "estimateEndDate": "2025-03-29"
      },
      {
        "id": "fr/enigmes/2025-03-30/2025-04-05",
        "estimateStartDate": "2025-03-30",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 105,
        "estimateEndDate": "2025-04-05"
      },
      {
        "id": "fr/enigmes/2025-04-06/2025-04-12",
        "estimateStartDate": "2025-04-06",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 105,
        "estimateEndDate": "2025-04-12"
      },
      {
        "id": "fr/enigmes/2025-04-13/2025-04-19",
        "estimateStartDate": "2025-04-13",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 105,
        "estimateEndDate": "2025-04-19"
      },
      {
        "id": "fr/enigmes/2025-04-20/2025-04-26",
        "estimateStartDate": "2025-04-20",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 105,
        "estimateEndDate": "2025-04-26"
      },
      {
        "id": "fr/enigmes/2025-04-27/2025-05-03",
        "estimateStartDate": "2025-04-27",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 105,
        "estimateEndDate": "2025-05-03"
      },
      {
        "id": "fr/enigmes/2025-05-04/2025-05-10",
        "estimateStartDate": "2025-05-04",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 105,
        "estimateEndDate": "2025-05-10"
      },
      {
        "id": "fr/enigmes/2025-05-11/2025-05-17",
        "estimateStartDate": "2025-05-11",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 105,
        "estimateEndDate": "2025-05-17"
      },
      {
        "id": "fr/enigmes/2025-05-18/2025-05-24",
        "estimateStartDate": "2025-05-18",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 105,
        "estimateEndDate": "2025-05-24"
      },
      {
        "id": "fr/enigmes/2025-05-25/2025-05-31",
        "estimateStartDate": "2025-05-25",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 105,
        "estimateEndDate": "2025-05-31"
      },
      {
        "id": "fr/enigmes/2025-06-01/2025-06-07",
        "estimateStartDate": "2025-06-01",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 105,
        "estimateEndDate": "2025-06-07"
      },
      {
        "id": "fr/enigmes/2025-06-08/2025-06-14",
        "estimateStartDate": "2025-06-08",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 105,
        "estimateEndDate": "2025-06-14"
      },
      {
        "id": "fr/enigmes/2025-06-15/2025-06-21",
        "estimateStartDate": "2025-06-15",
        "type": "historical_keyword_search_volume",
        "estimatedExactSearchVolume": 105,
        "estimateEndDate": "2025-06-21"
      }
    ]
  }
}

Online test

Execute the current API with your API key and JSON payload. Online tests use this site's configured API environment; the Endpoint and copyable examples use the public integration address.

Recent Avg. 132 · Range 67–133 credits / callAPI usage records

Try it

Send a real request with the same contract shown in the reference.

Endpoint

/js/keywords/historical-search-volume

MCP method

nexscope_amazon_keyword_search_history

API key*

JSON payload*

cURL

curl -X POST \
  https://api.nexscope.ai/js/keywords/historical-search-volume \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "endDate": "2026-03-31", "keyword": "yoga mat", "marketplace": "us", "startDate": "2025-10-01" }'

Response

No response yet. Run the request to see the response here.

Related APIs

Amazon Keyword Expansion

Find related Amazon keywords and compare search demand.

Amazon Keyword Share Of Voice

Compare how often brands appear in Amazon's organic and sponsored search results.

Amazon Product Database

Find Amazon products by category, price, sales, reviews, and seller type.

Amazon Product Research

Browse Amazon product research APIs and choose the one that fits your task.