Amazon Intelligence SS: traffic/keyword API

Use Amazon Intelligence SS: traffic/keyword API through Nexscope with documented parameters, structured results and API key authentication.

CostRecent Avg. 32 · Range 16–32 credits / call

Try online

POST · https://api.nexscope.ai/ss/traffic/keywordMCP · nexscope_data_ss_traffic_keyword

Amazon Intelligence SS

What this API does

Use Amazon Intelligence SS: traffic/keyword API through Nexscope with documented parameters, structured results and API key authentication. The request accepts marketplace, asin, month, page, size. Its documented result includes marketplace, asin, summaryList, keywords, keyword, keywordCn, trafficKeywordType, conversionKeywordType.

Amazon Intelligence SS: traffic/keyword API API use cases

Build a keyword shortlist

To build a keyword shortlist, a marketplace analyst submits marketplace and asin to Amazon Intelligence SS: traffic/keyword API. The returned marketplace, asin, summaryList help choose candidate search terms for further investigation.

Compare search demand signals

A marketplace analyst uses Amazon Intelligence SS: traffic/keyword API with marketplace and asin to compare search demand signals. The returned marketplace, asin, summaryList help compare keyword demand within the requested market scope.

Plan a content or advertising test

For this workflow, a marketplace analyst calls Amazon Intelligence SS: traffic/keyword API with marketplace and asin to plan a content or advertising test. The result helps select terms for a content or advertising experiment.

Amazon Intelligence SS: traffic/keyword API API FAQ

What does the Amazon Intelligence SS: traffic/keyword API API return?

Use Amazon Intelligence SS: traffic/keyword API through Nexscope with documented parameters, structured results and API key authentication. The documented output includes marketplace, asin, summaryList, keywords, keyword, keywordCn, trafficKeywordType, conversionKeywordType. It corresponds to the supplied marketplace, asin, month, page, size. 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 Intelligence SS: traffic/keyword API API cost?

The current documented cost is Recent Avg. 32 · Range 16–32 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 Intelligence SS: traffic/keyword API API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/ss/traffic/keyword 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_ss_traffic_keyword. 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/ss/traffic/keyword

MCP method

nexscope_data_ss_traffic_keyword

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/ss/traffic/keyword

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/ss/traffic/keyword' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "asin": "B0XXXXXXXXX",
  "marketplace": "US",
  "page": 1,
  "size": 50
}'

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 Intelligence SS

POSThttps://api.nexscope.ai/ss/traffic/keyword

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/ss/traffic/keyword`
Auth	`Bearer API key`
Content-Type	`application/json`

Request parameters

Name	Type	Required	Description
`marketplace`	`string`	required	Market site, see marketplace optional value Example: US
`asin`	`string`	required	Product ASIN to be reverse-checked, maxLength 1000
`month`	`string`	optional	Historical month, format `yyyyMM`
`page`	`integer`	optional	Current page Example: 1
`size`	`integer`	optional	Number of items per page, minimum 1, maximum 100, maximum query 2000 Example: 50
`keyword`	`string`	optional	Keyword filtering, maxLength 1000
`badges`	`string`	optional	Exposure position, multiple values are separated by commas, see badges enumeration
`trafficKeywordTypes`	`string`	optional	Traffic proportion type, multiple values are separated by English commas, see trafficKeywordTypes enumeration
`conversionKeywordTypes`	`string`	optional	Traffic conversion type, multiple values are separated by English commas, see conversionKeywordTypes enumeration
`orderField`	`string`	optional	Ordering field, see orderField optional value Example: rankPosition
`orderDesc`	`boolean`	optional	Sort in reverse order Example: false

Code example

{
  "asin": "B0XXXXXXXXX",
  "marketplace": "US",
  "page": 1,
  "size": 50
}

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

Name	Type	Required	Description
`total`	`integer`	optional	Total number of items
`marketplace`	`string`	optional	market code
`asin`	`string`	optional	Query ASIN
`data`	`array`	optional	Traffic word list (corresponding to third-party `data.items`)
`summaryList`	`array`	optional	High frequency word summary list
`columns`	`array`	optional	Column definition
`costToken`	`integer`	optional	Consume token
`type`	`string`	optional	rendering style
`total`	`integer`	optional	Total times
`keywords`	`string`	optional	word
`keyword`	`string`	optional	keywords
`keywordCn`	`string`	optional	Keywords Chinese translation
`trafficKeywordType`	`string`	optional	Traffic proportion type
`conversionKeywordType`	`string`	optional	Traffic conversion type
`badges`	`array`	optional	Exposure position (traffic word type)
`rankPosition`	`object`	optional	Natural ranking position information, see ranking object for structure
`adPosition`	`object`	optional	Ad ranking information, the structure is the same as the ranking object
`searches`	`integer`	optional	Monthly searches
`searchesRank`	`integer`	optional	Weekly search volume ranking
`searchesRankTimeFrom`	`integer`	optional	Weekly search volume ranking time range from
`searchesRankTimeTo`	`integer`	optional	Weekly search volume ranking time range ends
`purchases`	`integer`	optional	Monthly purchase volume
`purchaseRate`	`number`	optional	purchase rate
`products`	`integer`	optional	Number of items
`supplyDemandRatio`	`number`	optional	Supply and demand ratio
`trafficPercentage`	`number`	optional	Traffic proportion
`naturalRatio`	`number`	optional	Traffic distribution-natural proportion
`adRatio`	`number`	optional	Traffic distribution-advertising proportion
`calculatedWeeklySearches`	`number`	optional	Estimated weekly exposure
`impressions`	`integer`	optional	Impression volume
`clicks`	`integer`	optional	Clicks
`bid`	`number`	optional	PPC bidding
`bidMin`	`number`	optional	PPC bid minimum
`bidMax`	`number`	optional	PPC bid cap
`latest1daysAds`	`integer`	optional	Number of advertising competitors in the last day
`latest7daysAds`	`integer`	optional	Number of advertising competitors in the last 7 days
`latest30daysAds`	`integer`	optional	Number of competing advertising products in the last 30 days
`sprt`	`number`	optional	SP correlation ratio
`monopolyClickRate`	`number`	optional	Monopoly click rate
`top3ClickingRate`	`number`	optional	Top3 click rate
`top3ConversionRate`	`number`	optional	Top3 conversion rate
`titleDensity`	`number`	optional	title density
`stats`	`array`	optional	High-frequency words, the elements are shown in the table below
`updatedTime`	`integer`	optional	Update time
`keywords`	`string`	optional	word
`total`	`integer`	optional	Total number of items
`rankPosition`	`object`	optional	Natural ranking position, see ranking object for structure
`adPosition`	`object`	optional	Ad ranking position, see ranking object for structure
`updatedTime`	`integer`	optional	Ranking time
`pageSize`	`integer`	optional	How many pieces of data per page
`index`	`integer`	optional	What is the current page ranking?
`page`	`integer`	optional	Which page
`position`	`integer`	optional	What is the ranking among the total results?

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_ss_traffic_keyword",
    "arguments": {
      "asin": "B0XXXXXXXXX",
      "marketplace": "US",
      "page": 1,
      "size": 50
    }
  }
}

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.

21 credits / callAPI usage records

Try it

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

Endpoint

/ss/traffic/keyword

MCP method

nexscope_data_ss_traffic_keyword

API key*

JSON payload*

cURL

curl -X POST \
  https://api.nexscope.ai/ss/traffic/keyword \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "asin": "B0XXXXXXXXX", "marketplace": "US", "page": 1, "size": 50 }'

Response

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

Use Amazon Intelligence SS: competitor lookup API through Nexscope with documented parameters, structured results and API key authentication.

Amazon Intelligence SS: market/research API

Use Amazon Intelligence SS: market/research API through Nexscope with documented parameters, structured results and API key authentication.

Amazon Intelligence SS: market/statistics API

Use Amazon Intelligence SS: market/statistics API through Nexscope with documented parameters, structured results and API key authentication.

Amazon Intelligence SS: product Search API

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

What this API does

Amazon Intelligence SS: traffic/keyword API API use cases

Build a keyword shortlist

Compare search demand signals

Plan a content or advertising test

Amazon Intelligence SS: traffic/keyword API API FAQ

What does the Amazon Intelligence SS: traffic/keyword API API return?

How many credits does the Amazon Intelligence SS: traffic/keyword API API cost?

How do I call the Amazon Intelligence SS: traffic/keyword API API from my app or an MCP client?

Authentication

Run an API

Example request

Check the response

HTTP status codes

Run this API

Endpoint

Request parameters

Code example

Response example

Response fields

Responses

Data source, freshness, and limitations

MCP

Call a tool

Legacy MCP v1

Online test

Try it

Related APIs