Nexscope

Amazon Search Intelligence SF: asin Keywords API

Use Amazon Search Intelligence SF: asin Keywords API through Nexscope with documented parameters, structured results and API key authentication.

CostRecent Avg. 19 · Range 10–19 credits / call
Try online
POST · https://api.nexscope.ai/sf/asinKeywordsMCP · nexscope_data_sf_asin_keywords
Amazon Search Intelligence SF

What this API does

Use Amazon Search Intelligence SF: asin Keywords API through Nexscope with documented parameters, structured results and API key authentication. The request accepts asin, country, keyword, timePieceType, timePieceValue. Its documented result includes title, isParentAsin, hasVaiants, abaCreateDateWeek, keyword, translateKeyword, asin, productNaturalRank.

Amazon Search Intelligence SF: asin Keywords API API use cases

Build a keyword shortlist

To build a keyword shortlist, a marketplace analyst submits asin and country to Amazon Search Intelligence SF: asin Keywords API. The returned title, isParentAsin, hasVaiants help choose candidate search terms for further investigation.

Compare search demand signals

A marketplace analyst uses Amazon Search Intelligence SF: asin Keywords API with asin and country to compare search demand signals. The returned title, isParentAsin, hasVaiants help compare keyword demand within the requested market scope.

Plan a content or advertising test

For this workflow, a marketplace analyst calls Amazon Search Intelligence SF: asin Keywords API with asin and country to plan a content or advertising test. The result helps select terms for a content or advertising experiment.

Amazon Search Intelligence SF: asin Keywords API API FAQ

What does the Amazon Search Intelligence SF: asin Keywords API API return?

Use Amazon Search Intelligence SF: asin Keywords API through Nexscope with documented parameters, structured results and API key authentication. The documented output includes title, isParentAsin, hasVaiants, abaCreateDateWeek, keyword, translateKeyword, asin, productNaturalRank. It corresponds to the supplied asin, country, keyword, timePieceType, timePieceValue. 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 Search Intelligence SF: asin Keywords API API cost?

The current documented cost is Recent Avg. 19 · Range 10–19 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 Search Intelligence SF: asin Keywords API API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/sf/asinKeywords 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_sf_asin_keywords. 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/sf/asinKeywords
MCP method
nexscope_data_sf_asin_keywords

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/sf/asinKeywords

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/sf/asinKeywords' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "asin": "B0XXXXXXXX",
  "country": "US",
  "desc": true,
  "pageSize": 100,
  "sortBy": "estSearchesNum"
}'

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 Search Intelligence SF
POSThttps://api.nexscope.ai/sf/asinKeywords

Run this API

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

Endpoint

MethodPOST
Pathhttps://api.nexscope.ai/sf/asinKeywords
AuthBearer API key
Content-Typeapplication/json

Request parameters

NameTypeRequiredDescription
asinstringrequired
ASIN code, maximum length 1000 characters; only one ASIN can be queried at a time
countrystringoptional
Site: `US`, `UK`, `DE`, `CA`, `JP`, `FR`, `ES`, `IT`, `MX`, `AU`, `AE`, `BR`, `SA`
Example: US
keywordstringoptional
Keyword filtering, maximum length 1000; try to use the target site language
timePieceTypestringoptional
Time type: `latelyDay`, `month`, `week`
Example: latelyDay
timePieceValuestringoptional
Time slice value, maximum length 1000; `latelyDay` only supports `7` or `30`; `month` is `YYYY-MM`; `week` is the week start date `YYYY-MM-DD`
Example: 7
conditionsstringoptional
Comma separated conditions: `nfPosition`, `isSpAd`, `isBrandAd`, `isVedioAd`, `isAC`, `isAccurateKw`, `isAccurateTailKw`, `isPurchaseKw`, `isQualityKw`, `isStableKw`, `isLossKw`, `isInvalidKw`, `isMultiVariantKw`, `isSearchVolUpKw`, `isSearchVolDownKw`; cycle condition: `totalPeriod.in`、`nfKeywordCnt.total`/`.in`、`adKeywordCnt.total`/`.in`、`allSpKeywordCnt.total`/`.in`、`spKeywordCnt.total`/`.in`、`recSpKeywordCnt.total`/`.in`、`allSbKeywordCnt.total`/`.in`、`sbKeywordCnt.total`/`.in`、`sbvKeywordCnt.total`/`.in`
sortBystringoptional
`lastRank`、`adLastRank`、`updateTime`、`searchesRank`、`estSearchesNum`
descbooleanoptional
Is descending order
Example: true
pageNumintegeroptional
Page number
Example: 1
pageSizeintegeroptional
Number per page, range 10–100
Example: 100

Code example

{
  "asin": "B0XXXXXXXX",
  "country": "US",
  "desc": true,
  "pageSize": 100,
  "sortBy": "estSearchesNum"
}

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

NameTypeRequiredDescription
codestringoptional
sf business return code, `"1"` indicates success
msgstringoptional
news
totalintegeroptional
The actual amount of data returned this time
dataarrayoptional
keyword data array
columnsarrayoptional
render column
typestringoptional
rendering style
titlestringoptional
Title
isParentAsinbooleanoptional
Is it a parent ASIN?
hasVaiantsbooleanoptional
Are there any variants?
abaCreateDateWeekstringoptional
The latest weekly ABA data corresponds to the weekly time
costTimeintegeroptional
Time consuming (ms)
costTokenintegeroptional
Consume token
keywordstringoptional
keywords
translateKeywordstringoptional
Site localization translation
asinstringoptional
Product ASIN
productNaturalRankintegeroptional
Natural search ranking
naturalRankDisplaystringoptional
Natural ranking display text
productAdRankintegeroptional
SP Ad Rank
adRankDisplaystringoptional
Ad rank display text
weeklySearchVolumeintegeroptional
Estimated search volume per week
keywordPopularityRankintegeroptional
Keyword popularity ranking. The smaller the value, the greater the search volume.
totalSearchResultProductCountintegeroptional
Total number of search results items
trafficSharenumberoptional
The proportion of traffic this keyword brings to ASIN, 1 means 100%
naturalTrafficSharenumberoptional
Natural traffic score proportion
paidTrafficSharenumberoptional
Proportion of paid advertising traffic score (SP+SB+SBV+recommended advertising)
naturalTrafficScorenumberoptional
Natural Search Exposure Score
sponsoredProductsScorenumberoptional
SP regular bit score
brandAdScorenumberoptional
SB Brand Advertising Score (Regular + Video)
videoAdScorenumberoptional
SBV Video Ad Score
sponsoredRecommendationScorenumberoptional
SP recommendation total score
sponsoredRecommendationBreakdownarrayoptional
Recommendation bit details, each item is `{title, score, scoreRatio}`
clickConcentrationSharenumberoptional
ABA TOP3 click concentration, not conversion rate
clickToPurchaseConversionRatenumberoptional
Click-to-purchase conversion rate (`purchaseQty / clickQty`)
displayPositionTypesarrayoptional
Placement: `natural`, `ac`, `sp`, `top`, `bottom`, `er`, `vedio`, `tr`, `trfob`
trafficCharacteristicMarkersarrayoptional
Traffic tags: `isMainKw`, `isAccurateKw`, `isAccurateAboveKw`, `isAccurateTailKw`
conversionPerformanceMarkersarrayoptional
Conversion tags: `isPurchaseKw`, `isQualityKw`, `isStableKw`, `isLossKw`, `isInvalidKw`
lastNaturalRankTimestringoptional
The most recent effective natural ranking time
lastAdRankTimestringoptional
Last effective SP ad ranking time
periodEndDatestringoptional
End date of this cycle
updateTimestringoptional
Keyword data update time

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_sf_asin_keywords",
    "arguments": {
      "asin": "B0XXXXXXXX",
      "country": "US",
      "desc": true,
      "pageSize": 100,
      "sortBy": "estSearchesNum"
    }
  }
}

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.

12 credits / callAPI usage records

Try it

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

Endpoint
/sf/asinKeywords
MCP method
nexscope_data_sf_asin_keywords
cURL
curl -X POST \
  https://api.nexscope.ai/sf/asinKeywords \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "asin": "B0XXXXXXXX", "country": "US", "desc": true, "pageSize": 100, "sortBy": "estSearchesNum" }'
Response
No response yet. Run the request to see the response here.

Related APIs