Nexscope

Amazon Ads: sp/ad Groups/list API

Use Amazon Ads: sp/ad Groups/list API through Nexscope with documented parameters, structured results and API key authentication.

Cost10 credits / call
Try online
POST · https://api.nexscope.ai/amazonAds/sp/adGroups/listMCP · nexscope_data_amazon_ads_developer_proxy_sp_ad_groups_list
Amazon Ads

What this API does

Use Amazon Ads: sp/ad Groups/list API through Nexscope with documented parameters, structured results and API key authentication. The request accepts connectionId, fetchAll, maxResults, skipDepCheck, includeExtendedDataFields. Its documented result includes success, apiVersion, amazonResourceVersion, adGroups, pagesFetched, truncated, name, state.

Amazon Ads: sp/ad Groups/list API API use cases

Review advertising evidence

To review advertising evidence, a marketplace analyst submits connectionId and fetchAll to Amazon Ads: sp/ad Groups/list API. The returned success, apiVersion, amazonResourceVersion help inspect the advertising information returned for the request.

Prepare an advertising research brief

A marketplace analyst uses Amazon Ads: sp/ad Groups/list API 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 Amazon Ads: sp/ad Groups/list API with connectionId and fetchAll to compare campaign inputs and results. The result helps compare campaign evidence without assuming performance improvements.

Amazon Ads: sp/ad Groups/list API API FAQ

What does the Amazon Ads: sp/ad Groups/list API API return?

Use Amazon Ads: sp/ad Groups/list API through Nexscope with documented parameters, structured results and API key authentication. The documented output includes success, apiVersion, amazonResourceVersion, adGroups, 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 Amazon Ads: sp/ad Groups/list 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: sp/ad Groups/list API API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/amazonAds/sp/adGroups/list 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_ad_groups_list. 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/sp/adGroups/list
MCP method
nexscope_data_amazon_ads_developer_proxy_sp_ad_groups_list

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/adGroups/list

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/adGroups/list' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "body": "{}",
  "contentType": "application/vnd.spAdGroup.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
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/sp/adGroups/list

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/adGroups/list
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 method; list query is `POST`.
bodystringoptional
The filter and Amazon native request body are placed in the body string; the paging method is subject to the `fetchAll` description of the corresponding interface.
contentTypestringoptional
application/vnd.spAdGroup.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.

Code example

{
  "body": "{}",
  "contentType": "application/vnd.spAdGroup.v3+json",
  "method": "POST"
}

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 (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).
adGroupsarrayoptional
Ad group query Array; 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
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_developer_proxy_sp_ad_groups_list",
    "arguments": {
      "body": "{}",
      "contentType": "application/vnd.spAdGroup.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

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/sp/adGroups/list
MCP method
nexscope_data_amazon_ads_developer_proxy_sp_ad_groups_list
cURL
curl -X POST \
  https://api.nexscope.ai/amazonAds/sp/adGroups/list \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "body": "{}", "contentType": "application/vnd.spAdGroup.v3+json", "method": "POST" }'
Response
No response yet. Run the request to see the response here.

Related APIs