Nexscope

Sponsored Products Campaign Target Exclusions

Work with campaign-level negative targets to exclude unwanted product or category targets from Sponsored Products campaigns.

Cost10 credits / call
Try online
POST · https://api.nexscope.ai/amazonAds/sp/campaignNegativeTargetsMCP · nexscope_data_amazon_ads_developer_proxy_sp_campaign_negative_targets

What this API does

Work with campaign-level negative targets to exclude unwanted product or category targets from Sponsored Products campaigns. The request accepts connectionId, fetchAll, maxResults, skipDepCheck, includeExtendedDataFields. Its documented result includes success, apiVersion, amazonResourceVersion, negativeTargetingClauses, pagesFetched, truncated, name, state.

Sponsored Products Campaign Target Exclusions API use cases

Review advertising evidence

To review advertising evidence, a marketplace analyst submits connectionId and fetchAll to Sponsored Products Campaign Target Exclusions. The returned success, apiVersion, amazonResourceVersion help inspect the advertising information returned for the request.

Prepare an advertising research brief

A marketplace analyst uses Sponsored Products Campaign Target Exclusions with connectionId and fetchAll to prepare an advertising research brief. The returned success, apiVersion, amazonResourceVersion help assemble evidence before changing an advertising workflow.

Compare campaign inputs and results

For this workflow, a marketplace analyst calls Sponsored Products Campaign Target Exclusions with connectionId and fetchAll to compare campaign inputs and results. The result helps compare campaign evidence without assuming performance improvements.

Sponsored Products Campaign Target Exclusions API FAQ

What does the Sponsored Products Campaign Target Exclusions API return?

Work with campaign-level negative targets to exclude unwanted product or category targets from Sponsored Products campaigns. The documented output includes success, apiVersion, amazonResourceVersion, negativeTargetingClauses, pagesFetched, truncated, name, state. It corresponds to the supplied connectionId, fetchAll, maxResults, skipDepCheck, includeExtendedDataFields. 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 Sponsored Products Campaign Target Exclusions 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 Sponsored Products Campaign Target Exclusions API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/amazonAds/sp/campaignNegativeTargets 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_sp_campaign_negative_targets. 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/amazonAds/sp/campaignNegativeTargets
MCP method
nexscope_data_amazon_ads_developer_proxy_sp_campaign_negative_targets

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/sp/campaignNegativeTargets

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/sp/campaignNegativeTargets' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "body": "{}",
  "contentType": "application/vnd.spCampaignNegativeTargetingClause.v3+json",
  "method": "POST"
}'

Code example

{
  "body": "{}",
  "contentType": "application/vnd.spCampaignNegativeTargetingClause.v3+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

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

Run this API

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

Endpoint

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

Request parameters

NameTypeRequiredDescription
connectionIdintegerrequired
An Amazon Ads connection owned by the authenticated Nexscope user.
fetchAllbooleanoptional
Automatic page turning; SP and SB V4 main resource lists use `nextToken`, SB Target/BudgetRule uses `nextToken` (BudgetRule query must contain `pageSize`), SB Keyword GET, SB V3 GET and SD use `startIndex + count`.
Example: true
maxResultsintegeroptional
Single page 1–100; SD corresponds to count.
Example: 100
skipDepCheckbooleanoptional
Skip dependency checking.
Example: false
includeExtendedDataFieldsbooleanoptional
Some entities return extended fields; SD is switched through the /extended path.
localestringoptional
Localization parameters (supported by some keyword scripts).
methodstringrequired
Upstream HTTP methods: `POST` creation, `PUT` modification.
bodystringrequired
The payload must be provided; the API will serialize it and forward it to the upstream, and the Amazon access token cannot be put into the payload.
contentTypestringoptional
application/vnd.spCampaignNegativeTargetingClause.v3+json。
queryStringstringoptional
Pass upstream query parameters when needed.
confirmationTokenstringoptional
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 (9 fields)

NameTypeRequiredDescription
successbooleanoptional
Whether the API completed the call successfully.
apiVersionstringoptional
`V3` or `V4` (if provided by the script).
amazonResourceVersionstringoptional
The actual Amazon resource version (if provided by the script).
negativeTargetingClausesarrayoptional
Array of activity-level negative product targeting; actual fields returned by Amazon.
totalintegeroptional
The number of aggregated entries (if provided by the script).
pagesFetchedintegeroptional
Number of pages obtained.
truncatedbooleanoptional
Whether it was truncated due to paging limit.
namestringoptional
Name (returned if supported by the entity).
statestringoptional
`ENABLED`, `PAUSED` or `ARCHIVED` (SD upstream may use lowercase).

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_data_amazon_ads_developer_proxy_sp_campaign_negative_targets",
    "arguments": {
      "body": "{}",
      "contentType": "application/vnd.spCampaignNegativeTargetingClause.v3+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

What can you do with this API?

Data explained and practical use cases

AI Guide

Question

What can Sponsored Products Campaign Target Exclusions provide, and how might I use it?

AI answer

This operation is for creating or updating campaign-level negative product or category targets. Its documented result may contain exclusion entries, though their individual fields are left to the upstream response.

Data categoryDocumented fieldWhat it means
Excluded targetsnegativeTargetingClausesAn optional array of campaign-level negative targeting clauses; item-level fields are not specified here.
Entry statusstateAn optional state such as ENABLED, PAUSED, or ARCHIVED.
Result counttotalThe number of aggregated entries, if supplied.
Paging completenesstruncated, pagesFetchedWhether paging limited the result and how many pages were obtained, if supplied.
  • Exclude a product target that is unsuitable across a campaign.
    • Prompt example: “I manage a connected Amazon Ads account. Could you exclude a product target that is unsuitable across a campaign? Show the relevant returned evidence and tell me what input you need from me.”
  • Update a campaign's category exclusions when its product focus changes.
    • Prompt example: “I want to change a category exclusion in the Sponsored Products campaign I identify. Ask me which target and setting to use, show the current exclusion and exact proposed update, and wait for my explicit approval. Then report only the returned negative-target data.”
  • Review returned clause states to identify exclusions that are paused or archived.
    • Prompt example: “I manage a connected Amazon Ads account. Could you review returned clause states to identify exclusions that are paused or archived? Show matching records and source links where the API provides them; ask me for any required identifier or filter.”

The example's data object is empty, so it does not establish which product or category identifiers, clause details, or mutation outcomes will appear.

Related APIs