Amazon Ads Custom Requests

Send an allowed Amazon Ads request through your connected account when you need an advertising operation beyond the individual tools.

Cost10 credits / call

Try online

POST · https://api.nexscope.ai/amazonAds/developerProxyMCP · nexscope_data_amazon_ads_developer_proxy_amazon_ads_developer_proxy

What this API does

Send an allowed Amazon Ads request through your connected account when you need an advertising operation beyond the individual tools. The request accepts connectionId, method, body, contentType, pollInterval. Its documented result includes success, reportId, reportKind, profileId, advertiserAccountId, fields, totalRows, dataFiles[].

Amazon Ads Custom Requests API use cases

Review advertising evidence

To review advertising evidence, a marketplace analyst submits connectionId and method to Amazon Ads Custom Requests. The returned success, reportId, reportKind help inspect the advertising information returned for the request.

Prepare an advertising research brief

A marketplace analyst uses Amazon Ads Custom Requests with connectionId and method to prepare an advertising research brief. The returned success, reportId, reportKind help assemble evidence before changing an advertising workflow.

Compare campaign inputs and results

For this workflow, a marketplace analyst calls Amazon Ads Custom Requests with connectionId and method to compare campaign inputs and results. The result helps compare campaign evidence without assuming performance improvements.

Amazon Ads Custom Requests API FAQ

What does the Amazon Ads Custom Requests API return?

Send an allowed Amazon Ads request through your connected account when you need an advertising operation beyond the individual tools. The documented output includes success, reportId, reportKind, profileId, advertiserAccountId, fields, totalRows, dataFiles[]. It corresponds to the supplied connectionId, method, body, contentType, pollInterval. 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 Custom Requests 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 Custom Requests API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/amazonAds/developerProxy 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_developer_proxy_amazon_ads_developer_proxy. 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 credits Connect this API with MCP

Try this API

Endpoint

https://api.nexscope.ai/amazonAds/developerProxy

MCP method

nexscope_data_amazon_ads_developer_proxy_amazon_ads_developer_proxy

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

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/developerProxy' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "body": "{}",
  "contentType": "application/json",
  "method": "POST"
}'

Code example

{
  "body": "{}",
  "contentType": "application/json",
  "method": "POST"
}

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	Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result.
429	Execution admission rate limit; honor Retry-After when present.
503	Execution admission is temporarily unavailable; honor Retry-After when present.
Opt-in	X-Nexscope-Http-Status: semantic maps controller-handled business errors to HTTP status on run and task routes. Pre-authentication failures, such as a missing API key (code 11209), 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.

View parameters & response Try online

All categories/ Amazon Ads

POSThttps://api.nexscope.ai/amazonAds/developerProxy

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/amazonAds/developerProxy`
Auth	`Bearer API key`
Content-Type	`application/json`

Request parameters

Name	Type	Required	Description
`connectionId`	`integer`	required	An Amazon Ads connection owned by the authenticated Nexscope user.
`method`	`string`	required	The three stages of Ads v1 are all `POST`.
`body`	`string`	required	JSON string; account query can be `{}`, report creation/polling see dedicated reference respectively.
`contentType`	`string`	optional	Typically `application/json`.
`pollInterval`	`integer`	optional	5–300 seconds; official recommendation is to poll every minute. Example: 60
`maxAttempts`	`integer`	optional	1–120, default waiting window of approximately 10 minutes. Example: 10
`reportId`	`string`	optional	After passing in, account mapping and creation will be skipped, and existing reports will only be polled.
`confirmationToken`	`string`	optional	For mutations, first preview without a token, then confirm using the returned single-use token.

Response example

Platform response envelope. code 0 indicates success or acceptance; data contains the business result.

No response example is published for this API. Refer to the response fields below.

Response fields

Response field reference (15 fields)

Name	Type	Required	Description
`success`	`boolean`	optional	Whether the entry script completes report processing.
`status`	`string`	optional	`PENDING`, `PROCESSING`, `COMPLETED`, `FAILED` or `STILL_PROCESSING`.
`reportId`	`string`	optional	Report ID.
`reportKind`	`string`	optional	`audience` or `search-impression-share`.
`profileId`	`number`	optional	Ads profile used.
`advertiserAccountId`	`string`	optional	The Ads v1 account ID mapped to.
`fields`	`array`	optional	The actual fixed field combination (as returned).
`totalRows`	`integer`	optional	The total number of rows after merging; 0 is a legally empty report.
`dataFiles[]`	`array`	optional	Local CSV slice file and row number.
`preview[]`	`array`	optional	Results preview.
`resumeHint`	`object`	optional	Continue parameters during STILL_PROCESSING.
`_cacheable`	`boolean`	optional	Successful results are cached for 24 hours; failed/incomplete is false.
`part`	`integer`	optional	Fragment serial number.
`path`	`string`	optional	Local CSV file path.
`rowCount`	`integer`	optional	The number of rows in this shard.

Responses

Code	Description
200	Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result.
429	Execution admission rate limit; honor Retry-After when present.
503	Execution admission is temporarily unavailable; honor Retry-After when present.
Opt-in	X-Nexscope-Http-Status: semantic maps controller-handled business errors to HTTP status on run and task routes. Pre-authentication failures, such as a missing API key (code 11209), 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_data_amazon_ads_developer_proxy_amazon_ads_developer_proxy",
    "arguments": {
      "body": "{}",
      "contentType": "application/json",
      "method": "POST"
    }
  }
}

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

MCP method

nexscope_data_amazon_ads_developer_proxy_amazon_ads_developer_proxy

API key*

JSON payload*

cURL

curl -X POST \
  https://api.nexscope.ai/amazonAds/developerProxy \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "body": "{}", "contentType": "application/json", "method": "POST" }'

Response

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

Related APIs

Amazon Ads API Access

Connect an Amazon Ads account and check its connection status.

Amazon Advertising

Manage Amazon Sponsored Products, Sponsored Brands, and Sponsored Display advertising.

Amazon Ads Connected Stores

List the stores connected to your Amazon Ads account so you can choose the account to use for campaign management.

Amazon Ads Account Report Creation

Create an advertiser account report for your selected request settings to review Amazon advertising results.