Nexscope

Amazon Ads: authorized Stores API

Use Amazon Ads: authorized Stores API through Nexscope with documented parameters, structured results and API key authentication.

Cost10 credits / call
Try online
POST · https://api.nexscope.ai/amazonAds/authorizedStoresMCP · nexscope_data_amazon_ads_authorized_stores
Amazon Ads

What this API does

Use Amazon Ads: authorized Stores API through Nexscope with documented parameters, structured results and API key authentication. Its documented result includes stores[], profileId, accountInfoId, accountInfoName, accountType, countryCode, marketplaceStringId, region.

Amazon Ads: authorized Stores API API use cases

Investigate a seller or store

To investigate a seller or store, a marketplace analyst submits the operation-specific inputs to Amazon Ads: authorized Stores API. The returned stores[], profileId, accountInfoId help identify the store associated with a candidate product.

Compare storefront product evidence

A marketplace analyst uses Amazon Ads: authorized Stores API with the operation-specific inputs to compare storefront product evidence. The returned stores[], profileId, accountInfoId help compare products or listings across shortlisted storefronts.

Shortlist stores for further research

For this workflow, a marketplace analyst calls Amazon Ads: authorized Stores API with the operation-specific inputs to shortlist stores for further research. The result helps choose stores for a supplier or competitor review.

Amazon Ads: authorized Stores API API FAQ

What does the Amazon Ads: authorized Stores API API return?

Use Amazon Ads: authorized Stores API through Nexscope with documented parameters, structured results and API key authentication. The documented output includes stores[], profileId, accountInfoId, accountInfoName, accountType, countryCode, marketplaceStringId, region. 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 Ads: authorized Stores 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 Ads: authorized Stores API API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/amazonAds/authorizedStores 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_amazon_ads_authorized_stores. 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/amazonAds/authorizedStores
MCP method
nexscope_data_amazon_ads_authorized_stores

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/amazonAds/authorizedStores

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/amazonAds/authorizedStores' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'

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 Ads
POSThttps://api.nexscope.ai/amazonAds/authorizedStores

Run this API

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

Endpoint

MethodPOST
Pathhttps://api.nexscope.ai/amazonAds/authorizedStores
AuthBearer API key
Content-Typeapplication/json

Request parameters

No required request fields are defined for this API.

Code example

{}

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

NameTypeRequiredDescription
totalintegeroptional
The number of authorized sites returned.
stores[]arrayoptional
Account × site authorization record.
profileIdnumberoptional
The profile ID used by downstream ad operations.
accountInfoIdstringoptional
Advertiser entity identifier.
accountInfoNamestringoptional
Store/advertiser name.
accountTypestringoptional
`seller`, `vendor` or `agency`.
countryCodestringoptional
Site country code.
marketplaceStringIdstringoptional
Amazon marketplace ID。
regionstringoptional
`NA`, `EU` or `FE`.
authRecordIdnumberoptional
Authorization record ID.
accountNamestringoptional
The account display name set during authorization.

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_amazon_ads_authorized_stores",
    "arguments": {}
  }
}

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
/amazonAds/authorizedStores
MCP method
nexscope_data_amazon_ads_authorized_stores
cURL
curl -X POST \
  https://api.nexscope.ai/amazonAds/authorizedStores \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{}'
Response
No response yet. Run the request to see the response here.

Related APIs