Nexscope

Amazon Ads: authorize Url API

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

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

What this API does

Use Amazon Ads: authorize Url API through Nexscope with documented parameters, structured results and API key authentication. The request accepts region, marketplaceId, workspaceId, accountName. Its documented result includes authorizeUrl, sourceType.

Amazon Ads: authorize Url API API use cases

Review advertising evidence

To review advertising evidence, a marketplace analyst submits region and marketplaceId to Amazon Ads: authorize Url API. The returned authorizeUrl, sourceType help inspect the advertising information returned for the request.

Prepare an advertising research brief

A marketplace analyst uses Amazon Ads: authorize Url API with region and marketplaceId to prepare an advertising research brief. The returned authorizeUrl, sourceType help assemble evidence before changing an advertising workflow.

Compare campaign inputs and results

For this workflow, a marketplace analyst calls Amazon Ads: authorize Url API with region and marketplaceId to compare campaign inputs and results. The result helps compare campaign evidence without assuming performance improvements.

Amazon Ads: authorize Url API API FAQ

What does the Amazon Ads: authorize Url API API return?

Use Amazon Ads: authorize Url API through Nexscope with documented parameters, structured results and API key authentication. The documented output includes authorizeUrl, sourceType. It corresponds to the supplied region, marketplaceId, workspaceId, accountName. 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: authorize Url 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: authorize Url API API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/amazonAds/authorizeUrl 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_authorize_url. 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/authorizeUrl
MCP method
nexscope_data_amazon_ads_authorize_url

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/authorizeUrl

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/authorizeUrl' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "accountName": "My US advertising account"
}'

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/authorizeUrl

Run this API

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

Endpoint

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

Request parameters

NameTypeRequiredDescription
regionstringrequired
Amazon Ads region.
Example: NA
marketplaceIdstringrequired
Amazon marketplace identifier for the Ads connection.
Example: ATVPDKIKX0DER
workspaceIdstringrequired
A Nexscope workspace accessible to the authenticated user.
accountNamestringoptional
Display name for the authorized account.

Code example

{
  "accountName": "My US advertising account"
}

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

NameTypeRequiredDescription
authorizeUrlstringoptional
Amazon Ads OAuth authorization URL.
sourceTypestringoptional
Authorization source identifier, fixed to `amazon_ads`.

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_authorize_url",
    "arguments": {
      "accountName": "My US advertising account"
    }
  }
}

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

Related APIs