Amazon History KP: product Series API

Use Amazon History KP: product Series API through Nexscope with documented parameters, structured results and API key authentication.

CostRecent 10 credits / call

Try online

POST · https://api.nexscope.ai/kp/productSeriesMCP · nexscope_data_kp_product_series

Amazon History KP

What this API does

Use Amazon History KP: product Series API through Nexscope with documented parameters, structured results and API key authentication. The request accepts asin, domain, days, showPrice, showPriceList. Its documented result includes asin, buyboxPrice, price, priceList, priceDeal, pricePrime, priceFba, priceFbm.

Amazon History KP: product Series API API use cases

Inspect a candidate product

To inspect a candidate product, a marketplace analyst submits asin and domain to Amazon History KP: product Series API. The returned asin, buyboxPrice, price help inspect the documented attributes of the candidate product.

Compare listing details

A marketplace analyst uses Amazon History KP: product Series API with asin and domain to compare listing details. The returned asin, buyboxPrice, price help compare product details with another shortlisted listing.

Prepare product evidence for a sourcing review

For this workflow, a marketplace analyst calls Amazon History KP: product Series API with asin and domain to prepare product evidence for a sourcing review. The result helps record product facts before a sourcing discussion.

Amazon History KP: product Series API API FAQ

What does the Amazon History KP: product Series API API return?

Use Amazon History KP: product Series API through Nexscope with documented parameters, structured results and API key authentication. The documented output includes asin, buyboxPrice, price, priceList, priceDeal, pricePrime, priceFba, priceFbm. It corresponds to the supplied asin, domain, days, showPrice, showPriceList. 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 History KP: product Series API API cost?

The current documented cost is Recent 10 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 History KP: product Series API API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/kp/productSeries 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_data_kp_product_series. The same documented request parameters apply; use Online test to review a request before adding it to your app.

View plans and credits Connect this API with MCP

Try this API

Endpoint

https://api.nexscope.ai/kp/productSeries

MCP method

nexscope_data_kp_product_series

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/kp/productSeries

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/kp/productSeries' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "asin": "B0DFRJ7WSX",
  "days": 90,
  "domain": "1",
  "showBsrMain": 1,
  "showPrice": 1,
  "showSellerCount": 1
}'

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	HTTP request completed. Check JSON code; only 0 indicates business success or acceptance.
400	Request JSON or required API parameters are invalid.
401	API key is missing, invalid, or cannot be matched to a user.
5xx	API execution or upstream service failed.

View parameters & response Try online

All categories/ Amazon History KP

POSThttps://api.nexscope.ai/kp/productSeries

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/kp/productSeries`
Auth	`Bearer API key`
Content-Type	`application/json`

Request parameters

Name	Type	Required	Description
`asin`	`string`	required	Amazon Standard Identification Number (ASIN), only supports a single ASIN, the maximum length is 1000.
`domain`	`string`	required	amazon domain name ID: `1` (USA), `2` (UK), `3` (Germany), `4` (France), `5` (Japan), `6` (Canada), `8` (Italy), `9` (Spain), `10` (India), `11` (Mexico), `12` (Brazil).
`days`	`integer`	optional	Limit the number of days of historical data to a maximum of `365`. Example: 90
`showPrice`	`integer`	optional	Set to `1` to return the lowest new product price curve in the market.
`showPriceList`	`integer`	optional	Set to `1` to return the strike/mark curve.
`showPriceDeal`	`integer`	optional	Set to `1` to return the flash sale price curve.
`showPricePrime`	`integer`	optional	Set to `1` to return Prime exclusive new product price curve.
`showPriceFba`	`integer`	optional	Set to `1` to return the third-party FBA new product price curve.
`showPriceFbm`	`integer`	optional	Set to `1` to return the third-party FBM new product price curve.
`showPriceCoupon`	`integer`	optional	Set to `1` Returns the post-coupon Buy Box price curve.
`showBsrMain`	`integer`	optional	Set to `1` to return the large class of BSR curves.
`showSellerCount`	`integer`	optional	Set to `1` to return the seller number curve.

Code example

{
  "asin": "B0DFRJ7WSX",
  "days": 90,
  "domain": "1",
  "showBsrMain": 1,
  "showPrice": 1,
  "showSellerCount": 1
}

Response example

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

{
  "code": 0,
  "cost": "-1",
  "data": {},
  "msg": null,
  "time": "2026-01-01 00:00:00",
  "traceId": null,
  "ts": "0"
}

Response fields

Response field reference (20 fields)

Name	Type	Required	Description
`asin`	`string`	optional	ASIN。
`buyboxPrice`	`array`	optional	Buy Box price; elements contain `time` (time) and `value` (Buy Box price).
`price`	`array`	optional	The lowest new product price on the market; elements include `time` and `value`.
`priceList`	`array`	optional	Strikethrough price; elements contain `time` and `value`.
`priceDeal`	`array`	optional	Deal price; elements contain `time` and `value`.
`pricePrime`	`array`	optional	Prime price; elements contain `time` and `value`.
`priceFba`	`array`	optional	FBA price; elements contain `time` and `value`.
`priceFbm`	`array`	optional	FBM price; elements contain `time` and `value`.
`priceCoupon`	`array`	optional	Coupon price; elements contain `time` and `value`.
`bsrMain`	`array`	optional	Category BSR; each element contains `categoryName` (category name) and `points` (time series point).
`bsrSub`	`array`	optional	Small class BSR; each element contains `categoryName` (category name) and `points` (time series point).
`sellerCount`	`array`	optional	Number of sellers; elements contain `time` and `value`.
`rating`	`array`	optional	Rating; elements contain `time` and `value`.
`ratingCount`	`array`	optional	Score number; elements contain `time` and `value`.
`monthlySold`	`array`	optional	Subbody sales; elements contain `time` and `value`.
`costToken`	`integer`	optional	Consume token.
`time`	`—`	optional	Time; the specific type shall be subject to the source file or upstream official documentation.
`value`	`—`	optional	The indicator value corresponding to the time point; the specific type shall be subject to the source file or upstream official documentation.
`categoryName`	`—`	optional	Category name; the specific type shall be subject to the source file or upstream official documentation.
`points`	`—`	optional	This category is a BSR time series point, and the elements include `time` and `value`; the specific type is subject to the source file or the upstream official document.

Responses

Code	Description
200	HTTP request completed. Check JSON code; only 0 indicates business success or acceptance.
400	Request JSON or required API parameters are invalid.
401	API key is missing, invalid, or cannot be matched to a user.
5xx	API execution or upstream service failed.

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_data_kp_product_series",
    "arguments": {
      "asin": "B0DFRJ7WSX",
      "days": 90,
      "domain": "1",
      "showBsrMain": 1,
      "showPrice": 1,
      "showSellerCount": 1
    }
  }
}

Legacy MCP v1

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

GET / POST /mcp/legacy

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.

10 credits / callAPI usage records

Try it

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

Endpoint

/kp/productSeries

MCP method

nexscope_data_kp_product_series

API key*

JSON payload*

cURL

curl -X POST \
  https://api.nexscope.ai/kp/productSeries \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "asin": "B0DFRJ7WSX", "days": 90, "domain": "1", "showBsrMain": 1, "showPrice": 1, "showSellerCount": 1 }'

Response

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

Related APIs

Amazon History KP: product Request API

Use Amazon History KP: product Request API through Nexscope with documented parameters, structured results and API key authentication.

Amazon History KP: product Search API

Use Amazon History KP: product Search API through Nexscope with documented parameters, structured results and API key authentication.