Amazon Ads Sponsored Products Insights Reports
Scope
Amazon Ads Reporting API v1 beta audience performance and search-term impression share/rank reports, including advertiser-account mapping, report creation, polling, and multipart CSV download.
Requires an existing Amazon Ads connection through ecommerce-amazon-ads-api-access. It does not replace ordinary SP search-term performance, Sponsored Brands, Sponsored Display, or DSP reporting.
Read references/api.md for the authoritative contract and references/api.json for the machine-readable operation catalog.
Operations
| Script |
NexScope route |
get_sp_audience_report.py |
POST /api/v1/tools/research/amazonAds/developerProxy |
get_sp_search_impression_share.py |
POST /api/v1/tools/research/amazonAds/developerProxy |
Authentication and safety
- Set
NEXSCOPE_PROXY_BASE and NEXSCOPE_API_KEY. Send the NexScope key as Authorization: Bearer <key>.
- This skill requires
ecommerce-amazon-ads-api-access and an authorized Amazon Ads connection. Resolve the intended profile before requesting a report; never accept Amazon access or refresh tokens.
- Follow the online Ads packages' connection lifecycle: authorization state, OAuth exchange, encrypted credentials, token refresh, profile discovery, and provider request signing remain backend-owned.
- The allowlisted v1 beta operations still use the dedicated NexScope
developerProxy; do not substitute direct Amazon endpoints or the v3 reporting workflow.
- Provider credentials and upstream tokens remain backend-owned. Never accept, print, or persist them.
- Treat HTTP 401 as NexScope authentication failure and HTTP 402 as insufficient NexScope credits.
- Do not substitute another account, market, region, creator, product, or operation after an authorization or ambiguous network failure.
- This operation consumes credits. Preserve
X-Cost-Token and X-Cost-Credit from response headers as server-reported billing metadata.
Workflow
- Identify the exact operation, market/account context, filters, dates, pagination, and requested output.
- Validate required fields, types, enums, ranges, and operation-specific limits against
references/api.md before any request.
- Explain that additional pages, markets, or operations may consume more credits and obtain approval before a paid call.
- Run only the selected entry script, for example:
python scripts/get_sp_audience_report.py '<JSON parameters>' --no-cache when the script supports that flag.
- Preserve the full response under
nexscope/<date>/<session>/data; return a concise summary and the saved path.
- On an ambiguous timeout or upstream failure, do not retry automatically. Report the trace ID and reconcile state first.
Output rules
- Distinguish the NexScope transport envelope from the nested business response.
- Report only returned facts. Preserve absent values as unknown and keep provider-specific metric definitions intact.
- Never expose API keys, provider tokens, presigned URL query strings, internal account records, or raw secrets.
- Do not submit feedback or make any unrelated external mutation unless the user explicitly requests it.
Authentication
Set the NEXSCOPE_API_KEY environment variable. If credentials are missing or expire, visit https://www.nexscope.ai/help/skills-external-access?co-from=skillNS to top up credits.
1---2name: ecommerce-amazon-ads-sp-insights-report3description: Retrieve Amazon Ads Sponsored Products audience and search-term impression-share reports through NexScope.4---56# Amazon Ads Sponsored Products Insights Reports78## Scope910Amazon Ads Reporting API v1 beta audience performance and search-term impression share/rank reports, including advertiser-account mapping, report creation, polling, and multipart CSV download.1112Requires an existing Amazon Ads connection through ecommerce-amazon-ads-api-access. It does not replace ordinary SP search-term performance, Sponsored Brands, Sponsored Display, or DSP reporting.1314Read [references/api.md](references/api.md) for the authoritative contract and `references/api.json` for the machine-readable operation catalog.1516## Operations1718| Script | NexScope route |19|---|---|20| `get_sp_audience_report.py` | `POST /api/v1/tools/research/amazonAds/developerProxy` |21| `get_sp_search_impression_share.py` | `POST /api/v1/tools/research/amazonAds/developerProxy` |2223## Authentication and safety2425- Set `NEXSCOPE_PROXY_BASE` and `NEXSCOPE_API_KEY`. Send the NexScope key as `Authorization: Bearer <key>`.26- This skill requires `ecommerce-amazon-ads-api-access` and an authorized Amazon Ads connection. Resolve the intended profile before requesting a report; never accept Amazon access or refresh tokens.27- Follow the online Ads packages' connection lifecycle: authorization state, OAuth exchange, encrypted credentials, token refresh, profile discovery, and provider request signing remain backend-owned.28- The allowlisted v1 beta operations still use the dedicated NexScope `developerProxy`; do not substitute direct Amazon endpoints or the v3 reporting workflow.29- Provider credentials and upstream tokens remain backend-owned. Never accept, print, or persist them.30- Treat HTTP 401 as NexScope authentication failure and HTTP 402 as insufficient NexScope credits.31- Do not substitute another account, market, region, creator, product, or operation after an authorization or ambiguous network failure.32- This operation consumes credits. Preserve `X-Cost-Token` and `X-Cost-Credit` from response headers as server-reported billing metadata.3334## Workflow35361. Identify the exact operation, market/account context, filters, dates, pagination, and requested output.372. Validate required fields, types, enums, ranges, and operation-specific limits against `references/api.md` before any request.383. Explain that additional pages, markets, or operations may consume more credits and obtain approval before a paid call.394. Run only the selected entry script, for example: `python scripts/get_sp_audience_report.py '<JSON parameters>' --no-cache` when the script supports that flag.405. Preserve the full response under `nexscope/<date>/<session>/data`; return a concise summary and the saved path.416. On an ambiguous timeout or upstream failure, do not retry automatically. Report the trace ID and reconcile state first.4243## Output rules4445- Distinguish the NexScope transport envelope from the nested business response.46- Report only returned facts. Preserve absent values as unknown and keep provider-specific metric definitions intact.47- Never expose API keys, provider tokens, presigned URL query strings, internal account records, or raw secrets.48- Do not submit feedback or make any unrelated external mutation unless the user explicitly requests it.495051## Authentication5253Set the `NEXSCOPE_API_KEY` environment variable. If credentials are missing or expire, visit [https://www.nexscope.ai/help/skills-external-access?co-from=skillNS](https://www.nexscope.ai/help/skills-external-access?co-from=skillNS) to top up credits.
nexscope-ai