Nexscope

Amazon SP-API Refresh Seller Connection

Prepare an owned Amazon Seller credential and refresh it when required. The result reports readiness and expiry while keeping credentials on the server.

Cost10 credits / call
Try online
POST · https://api.nexscope.ai/spapi/refreshConnectionMCP · nexscope_amazon_sp_api_auth_refresh_connection

What this API does

Prepare an owned Amazon Seller credential and refresh it when required. The result reports readiness and expiry while keeping credentials on the server. The request accepts connectionId. Its documented result includes dataSnapshotMonth, expiresAt, page, pageItemCount, pageSize, prepared, sourceTool, sourceType.

Amazon SP-API Refresh Seller Connection API use cases

Investigate Amazon SP-API Refresh Seller Connection

To investigate amazon sp-api refresh seller connection, a marketplace analyst submits connectionId to Amazon SP-API Refresh Seller Connection. The returned dataSnapshotMonth, expiresAt, page help investigate the requested operation.

Collect Amazon SP-API Refresh Seller Connection evidence

A marketplace analyst uses Amazon SP-API Refresh Seller Connection with connectionId to collect amazon sp-api refresh seller connection evidence. The returned dataSnapshotMonth, expiresAt, page help compare evidence for the requested scope.

Review Amazon SP-API Refresh Seller Connection results

For this workflow, a marketplace analyst calls Amazon SP-API Refresh Seller Connection with connectionId to review amazon sp-api refresh seller connection results. The result helps review the returned facts with the team.

Amazon SP-API Refresh Seller Connection API FAQ

What does the Amazon SP-API Refresh Seller Connection API return?

Prepare an owned Amazon Seller credential and refresh it when required. The result reports readiness and expiry while keeping credentials on the server. The documented output includes dataSnapshotMonth, expiresAt, page, pageItemCount, pageSize, prepared, sourceTool, sourceType. It corresponds to the supplied connectionId. 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 SP-API Refresh Seller Connection 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 SP-API Refresh Seller Connection API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/spapi/refreshConnection 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_amazon_sp_api_auth_refresh_connection. Use the MCP arguments shown in the MCP guide, or switch Online test to MCP to review its request before adding it to your app.

View plans and creditsConnect this API with MCP

Try this API
Endpoint
https://api.nexscope.ai/spapi/refreshConnection
MCP method
nexscope_amazon_sp_api_auth_refresh_connection

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/spapi/refreshConnection

Run an API

Ensure a usable Amazon credential, refreshing it when needed.

Example request

Replace YOUR_API_KEY, then run this command in your terminal.

curl -X POST 'https://api.nexscope.ai/spapi/refreshConnection' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "connectionId": 123
}'

Code example

{
  "connectionId": 123
}

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
200Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result.
429Execution admission rate limit; honor Retry-After when present.
503Execution admission is temporarily unavailable; honor Retry-After when present.
Opt-inX-Nexscope-Http-Status: semantic maps controller-handled business errors to HTTP status on run and task routes. Pre-authentication failures, such as a missing or invalid API key (code 11209, including an incomplete or corrupted copy) or an expired website login session (code 12001), may still return HTTP 200 before this mapping. Always check the outer JSON code; malformed requests and infrastructure failures may also return non-200 HTTP responses.
All categories/ Amazon Selling Partner API
POSThttps://api.nexscope.ai/spapi/refreshConnection

Run this API

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

Endpoint

MethodPOST
Pathhttps://api.nexscope.ai/spapi/refreshConnection
AuthBearer API key
Content-Typeapplication/json

Request parameters

NameTypeRequiredDescription
connectionIdintegerrequired
Owned Seller connection ID.
Example: 123

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

NameTypeRequiredDescription
codeintegerrequired
0 means accepted or successful; nonzero is a platform error.
coststringrequired
Elapsed milliseconds, never credits; -1 outside web requests.
dataanyrequired
Data value used by this API operation.
msgstring | nullrequired
Msg value used by this API operation.
timestringrequired
Server local time: yyyy-MM-dd HH:mm:ss.
traceIdstring | nullrequired
Trace id value used by this API operation.
tsstringrequired
Epoch milliseconds.

Any of option 1 — requires prepared, expiresAt

NameTypeRequiredDescription
dataobjectrequired
Data value used by this API operation.
data.costTimeanyoptional
Cost time value used by this API operation.
data.costTokenanyoptional
Cost token value used by this API operation.
data.dataSnapshotMonthanyoptional
Data snapshot month value used by this API operation.
data.expiresAtintegerrequired
Credential expiry in milliseconds.
Example: null
data.pageanyoptional
Page value used by this API operation.
data.pageItemCountanyoptional
Page item count value used by this API operation.
data.pageSizeanyoptional
Page size value used by this API operation.
data.preparedbooleanrequired
Whether a usable credential was obtained.
Example: true
data.sourceToolanyoptional
Source tool value used by this API operation.
data.sourceTypeanyoptional
Source type value used by this API operation.
data.titleanyoptional
Title value used by this API operation.
data.totalPageanyoptional
Total page value used by this API operation.
data.typeanyoptional
Type value used by this API operation.

Any of option 1

NameTypeRequiredDescription
data.costTimeintegeroptional
Execution time reported by the upstream provider.
Example: null

Any of option 2

NameTypeRequiredDescription
data.costTimenulloptional
Cost time value used by this API operation.

Any of option 1

NameTypeRequiredDescription
data.costTokenintegeroptional
Token cost reported by the upstream provider.
Example: null

Any of option 2

NameTypeRequiredDescription
data.costTokennulloptional
Cost token value used by this API operation.

Any of option 1

NameTypeRequiredDescription
data.dataSnapshotMonthstringoptional
Data snapshot month returned by the upstream provider.
Example: null

Any of option 2

NameTypeRequiredDescription
data.dataSnapshotMonthnulloptional
Data snapshot month value used by this API operation.

Any of option 1

NameTypeRequiredDescription
data.pageintegeroptional
Current page returned by the upstream provider.
Example: null

Any of option 2

NameTypeRequiredDescription
data.pagenulloptional
Page value used by this API operation.

Any of option 1

NameTypeRequiredDescription
data.pageItemCountintegeroptional
Item count on the current page returned by the upstream provider.
Example: null

Any of option 2

NameTypeRequiredDescription
data.pageItemCountnulloptional
Page item count value used by this API operation.

Any of option 1

NameTypeRequiredDescription
data.pageSizeintegeroptional
Page size returned by the upstream provider.
Example: null

Any of option 2

NameTypeRequiredDescription
data.pageSizenulloptional
Page size value used by this API operation.

Any of option 1

NameTypeRequiredDescription
data.sourceToolstringoptional
Provider-specific source tool name.
Example: null

Any of option 2

NameTypeRequiredDescription
data.sourceToolnulloptional
Source tool value used by this API operation.

Any of option 1

NameTypeRequiredDescription
data.sourceTypestringoptional
Provider-specific source platform type.
Example: null

Any of option 2

NameTypeRequiredDescription
data.sourceTypenulloptional
Source type value used by this API operation.

Any of option 1

NameTypeRequiredDescription
data.titlestringoptional
Provider-specific response title.
Example: null

Any of option 2

NameTypeRequiredDescription
data.titlenulloptional
Title value used by this API operation.

Any of option 1

NameTypeRequiredDescription
data.totalPageintegeroptional
Total page count returned by the upstream provider.
Example: null

Any of option 2

NameTypeRequiredDescription
data.totalPagenulloptional
Total page value used by this API operation.

Any of option 1

NameTypeRequiredDescription
data.typestringoptional
Provider-specific render or payload type.
Example: null

Any of option 2

NameTypeRequiredDescription
data.typenulloptional
Type value used by this API operation.

Any of option 2

NameTypeRequiredDescription
datanullrequired
Data value used by this API operation.

Responses

CodeDescription
200Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result.
429Execution admission rate limit; honor Retry-After when present.
503Execution admission is temporarily unavailable; honor Retry-After when present.
Opt-inX-Nexscope-Http-Status: semantic maps controller-handled business errors to HTTP status on run and task routes. Pre-authentication failures, such as a missing or invalid API key (code 11209, including an incomplete or corrupted copy) or an expired website login session (code 12001), may still return HTTP 200 before this mapping. Always check the outer JSON code; malformed requests and infrastructure failures may also return non-200 HTTP responses.

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_amazon_sp_api_auth_refresh_connection",
    "arguments": {
      "connectionId": 123
    }
  }
}

What can you do with this API?

Data explained and practical use cases

AI Guide

Question

How do I check whether my Amazon Seller credential can be refreshed?

AI answer

Illustrative workflow and JSON use fictional values. Provide an owned connection ID and check prepared and expiresAt. The response deliberately omits access and refresh tokens.

Practical use case: Check whether my Amazon Seller credential can be refreshed.

Data Example

Illustrative request and response with fictional data

Request parameters

{
  "connectionId": 123
}

Response

{
  "code": 0,
  "data": {
    "prepared": true,
    "expiresAt": 1893456000000
  }
}

Related APIs