Nexscope

Amazon Research JS: keywords/share of voice API

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

CostRecent Avg. 128 · Range 67–133 credits / call
Try online
POST · https://api.nexscope.ai/js/keywords/share-of-voiceMCP · nexscope_data_js_keywords_share_of_voice
Amazon Research JS

What this API does

Use Amazon Research JS: keywords/share of voice API through Nexscope with documented parameters, structured results and API key authentication. The request accepts marketplace, keyword. Its documented result includes shareOfVoice, id, estimated30DaySearchVolume, exactSuggestedBidMedian, productCount, updatedAt, topAsinsModelStartDate, topAsinsModelEndDate.

Amazon Research JS: keywords/share of voice API API use cases

Check keyword visibility

To check keyword visibility, a marketplace analyst submits marketplace and keyword to Amazon Research JS: keywords/share of voice API. The returned shareOfVoice, id, estimated30DaySearchVolume help see which products appear for a target keyword.

Compare search placement evidence

A marketplace analyst uses Amazon Research JS: keywords/share of voice API with marketplace and keyword to compare search placement evidence. The returned shareOfVoice, id, estimated30DaySearchVolume help compare visibility evidence for the same search scope.

Prioritize keywords for a listing

For this workflow, a marketplace analyst calls Amazon Research JS: keywords/share of voice API with marketplace and keyword to prioritize keywords for a listing. The result helps choose keywords needing further listing or advertising research.

Amazon Research JS: keywords/share of voice API API FAQ

What does the Amazon Research JS: keywords/share of voice API API return?

Use Amazon Research JS: keywords/share of voice API through Nexscope with documented parameters, structured results and API key authentication. The documented output includes shareOfVoice, id, estimated30DaySearchVolume, exactSuggestedBidMedian, productCount, updatedAt, topAsinsModelStartDate, topAsinsModelEndDate. It corresponds to the supplied marketplace, keyword. 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/share of voice API API cost?

The current documented cost is Recent Avg. 128 · 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 Research JS: keywords/share of voice API API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/js/keywords/share-of-voice 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_share_of_voice. 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/share-of-voice
MCP method
nexscope_data_js_keywords_share_of_voice

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/share-of-voice

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/share-of-voice' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "keyword": "portable charger",
  "marketplace": "us"
}'

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/share-of-voice

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/share-of-voice
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
keywordstringrequired
Keywords to be searched

Code example

{
  "keyword": "portable charger",
  "marketplace": "us"
}

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

NameTypeRequiredDescription
costTokenintegeroptional
Number of tokens consumed
shareOfVoiceobjectoptional
Share of Voice data subject
idstringoptional
Resource ID
typestringoptional
Fixed value `share_of_voice`
estimated30DaySearchVolumeintegeroptional
Exact match search volume over the past 30 days
exactSuggestedBidMediannumberoptional
Median PPC bid (USD)
productCountintegeroptional
Total number of items in the first 3 pages of search results
updatedAtstringoptional
Data update time
topAsinsModelStartDatestringoptional
TOP ASIN click/conversion data window start date
topAsinsModelEndDatestringoptional
TOP ASIN click/conversion data window end date
brandsarrayoptional
Brand SOV detailed list
topAsinsarrayoptional
TOP 3 ASIN click conversion list
brandstringoptional
brand name
organicProductsintegeroptional
Number of items in organic search results
sponsoredProductsintegeroptional
The number of products in the ad slot
combinedProductsintegeroptional
Comprehensive product quantity
organicBasicSovnumberoptional
Natural search basics SOV (0–1)
organicWeightedSovnumberoptional
Natural search weighted SOV (0–1)
sponsoredBasicSovnumberoptional
Ad search basics SOV (0–1)
sponsoredWeightedSovnumberoptional
Ad Search Weighted SOV (0–1)
combinedBasicSovnumberoptional
Comprehensive Basic SOV (0–1)
combinedWeightedSovnumberoptional
Comprehensive weighted SOV (0–1)
organicAveragePositionnumberoptional
Average organic search ranking position
sponsoredAveragePositionnumberoptional
Ad search average position
combinedAveragePositionnumberoptional
Overall average ranking position
organicAveragePricenumberoptional
Average price of natural search items
sponsoredAveragePricenumberoptional
Average price of advertised search products
combinedAveragePricenumberoptional
Comprehensive product average price
asinstringoptional
ASIN number
namestringoptional
Product name
brandstringoptional
brand name
clicksintegeroptional
Clicks (30-day window)
conversionsintegeroptional
Conversions (30-day window)
conversionRatenumberoptional
Conversion rate (0-1)

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_share_of_voice",
    "arguments": {
      "keyword": "portable charger",
      "marketplace": "us"
    }
  }
}

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.

88 credits / callAPI usage records

Try it

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

Endpoint
/js/keywords/share-of-voice
MCP method
nexscope_data_js_keywords_share_of_voice
cURL
curl -X POST \
  https://api.nexscope.ai/js/keywords/share-of-voice \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "keyword": "portable charger", "marketplace": "us" }'
Response
No response yet. Run the request to see the response here.

Related APIs