Nexscope

Amazon Research JS: keywords/by asin API

Use Amazon Research JS: keywords/by asin API through Nexscope with documented parameters, structured results and API key authentication.

Cost10 credits / call
Try online
POST · https://api.nexscope.ai/js/keywords/by-asinMCP · nexscope_data_js_keywords_by_asin
Amazon Research JS

What this API does

Use Amazon Research JS: keywords/by asin API through Nexscope with documented parameters, structured results and API key authentication. The request accepts marketplace, asins, needCount, includeVariants, sort. Its documented result includes keywordInfoList, name, country, monthlySearchVolumeExact, monthlySearchVolumeBroad, monthlyTrend, quarterlyTrend, dominantCategory.

Amazon Research JS: keywords/by asin API API use cases

Build a keyword shortlist

To build a keyword shortlist, a marketplace analyst submits marketplace and asins to Amazon Research JS: keywords/by asin API. The returned keywordInfoList, name, country help choose candidate search terms for further investigation.

Compare search demand signals

A marketplace analyst uses Amazon Research JS: keywords/by asin API with marketplace and asins to compare search demand signals. The returned keywordInfoList, name, country help compare keyword demand within the requested market scope.

Plan a content or advertising test

For this workflow, a marketplace analyst calls Amazon Research JS: keywords/by asin API with marketplace and asins to plan a content or advertising test. The result helps select terms for a content or advertising experiment.

Amazon Research JS: keywords/by asin API API FAQ

What does the Amazon Research JS: keywords/by asin API API return?

Use Amazon Research JS: keywords/by asin API through Nexscope with documented parameters, structured results and API key authentication. The documented output includes keywordInfoList, name, country, monthlySearchVolumeExact, monthlySearchVolumeBroad, monthlyTrend, quarterlyTrend, dominantCategory. It corresponds to the supplied marketplace, asins, needCount, includeVariants, sort. 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 Research JS: keywords/by asin API API cost?

The current documented cost is 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 Research JS: keywords/by asin API API from my app or an MCP client?

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

View plans and creditsConnect this API with MCP

Try this API
Endpoint
https://api.nexscope.ai/js/keywords/by-asin
MCP method
nexscope_data_js_keywords_by_asin

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/by-asin

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/by-asin' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "asins": [
    "B0DXXXXXXX"
  ],
  "marketplace": "us",
  "needCount": 50,
  "sort": "-monthly_search_volume_exact"
}'

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

CodeDescription
200HTTP request completed. Check JSON code; only 0 indicates business success or acceptance.
400Request JSON or required API parameters are invalid.
401API key is missing, invalid, or cannot be matched to a user.
5xxAPI execution or upstream service failed.
All categories/ Amazon Research JS
POSThttps://api.nexscope.ai/js/keywords/by-asin

Run this API

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

Endpoint

MethodPOST
Pathhttps://api.nexscope.ai/js/keywords/by-asin
AuthBearer API key
Content-Typeapplication/json

Request parameters

NameTypeRequiredDescription
marketplacestringrequired
Target market code. Optional values: `us`, `uk`, `de`, `in`, `ca`, `fr`, `it`, `es`, `mx`, `jp`
Example: us
asinsstring[]required
List of ASINs, up to 10
needCountintegeroptional
Total number of results returned (internal automatic pagination)
includeVariantsbooleanoptional
Whether to include keywords for variant products
sortstringoptional
Sorting field; optional values ​​see the sorting field table below
Example: -monthly_search_volume_exact
minMonthlySearchVolumeExactintegeroptional
Minimum monthly precise search volume (1-999999)
maxMonthlySearchVolumeExactintegeroptional
Maximum monthly precise search volume (1-999999)
minMonthlySearchVolumeBroadintegeroptional
Minimum monthly broad search volume (1-999999)
maxMonthlySearchVolumeBroadintegeroptional
Maximum monthly broad search volume (1-999999)
minWordCountintegeroptional
Minimum number of words (1-99999)
maxWordCountintegeroptional
Maximum number of words (1-99999)
minOrganicProductCountintegeroptional
Minimum number of natural search results (1-99999)
maxOrganicProductCountintegeroptional
Maximum number of natural search results (1-99999)

Code example

{
  "asins": [
    "B0DXXXXXXX"
  ],
  "marketplace": "us",
  "needCount": 50,
  "sort": "-monthly_search_volume_exact"
}

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 (36 fields)

NameTypeRequiredDescription
costTokenintegeroptional
Number of tokens consumed
keywordInfoListarrayoptional
Keyword information list
namestringoptional
keywords
countrystringoptional
market code
monthlySearchVolumeExactintegeroptional
Monthly exact match search volume
monthlySearchVolumeBroadintegeroptional
Monthly broad match search volume
monthlyTrendfloatoptional
Month-on-month trend (%)
quarterlyTrendfloatoptional
Quarterly Trend (%)
dominantCategorystringoptional
Main categories
relevancyScoreintegeroptional
Relevance of keywords to ASIN (0-100)
easeOfRankingScoreintegeroptional
Ease of ranking (0-100, the higher it is, the easier it is to rank)
organicRankintegeroptional
ASIN’s organic search ranking
sponsoredRankintegeroptional
Ad Rank for ASIN
overallRankintegeroptional
Comprehensive ranking position
organicProductCountintegeroptional
Total number of products in organic search results
sponsoredProductCountintegeroptional
Total number of advertising space products
ppcBidExactfloatoptional
Exact match PPC recommended bid (USD)
ppcBidBroadfloatoptional
Broad Match PPC Recommended Bid (USD)
spBrandAdBidfloatoptional
SP Brand Ad Recommended Bid (USD)
recommendedPromotionsintegeroptional
Recommended promotion amount
primaryAsinstringoptional
The highest ranking ASIN for this keyword
relativeOrganicPositionfloatoptional
Query the relative natural ranking position of an ASIN
relativeSponsoredPositionfloatoptional
Query the relative ad ranking position of ASIN
organicRankingAsinsCountintegeroptional
Number of query ASINs with natural rankings
sponsoredRankingAsinsCountintegeroptional
Number of query ASINs with ad ranking
avgCompetitorOrganicRankfloatoptional
Query the average organic position of an ASIN
avgCompetitorSponsoredRankfloatoptional
Query the average ad position for an ASIN
variationLowestOrganicRankintegeroptional
Best organic position among variations
variationLowestSponsoredRankintegeroptional
Best ad position among variations
competitorOrganicRankarrayoptional
Natural ranking for each ASIN, element `{asin, organicRank}`
competitorSponsoredRankarrayoptional
Ad rank for each ASIN, element `{asin, sponsoredRank}`
updatedAtstringoptional
Data last updated time
asinstringoptional
ASIN
organicRankintegeroptional
The ASIN’s organic search ranking
asinstringoptional
ASIN
sponsoredRankintegeroptional
Ad Rank for this ASIN

Responses

CodeDescription
200HTTP request completed. Check JSON code; only 0 indicates business success or acceptance.
400Request JSON or required API parameters are invalid.
401API key is missing, invalid, or cannot be matched to a user.
5xxAPI 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_js_keywords_by_asin",
    "arguments": {
      "asins": [
        "B0DXXXXXXX"
      ],
      "marketplace": "us",
      "needCount": 50,
      "sort": "-monthly_search_volume_exact"
    }
  }
}

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
/js/keywords/by-asin
MCP method
nexscope_data_js_keywords_by_asin
cURL
curl -X POST \
  https://api.nexscope.ai/js/keywords/by-asin \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "asins": [ "B0DXXXXXXX" ], "marketplace": "us", "needCount": 50, "sort": "-monthly_search_volume_exact" }'
Response
No response yet. Run the request to see the response here.

Related APIs