Amazon Ads API

Amazon Ads API v3 skill for OpenClaw agents. List profiles, manage Sponsored Products campaigns, view budgets and performance. Works with any advertiser acco...

Security Scan

The skill's code and instructions match its stated purpose (managing Amazon Ads via LWA credentials); nothing in the files requests unrelated secrets or contacts unexpected endpoints, but the publisher is unverified and the skill stores sensitive tokens in a local JSON file so use caution.

Purpose & Capability

Name/description, SKILL.md, and scripts/ads.js are consistent: the skill implements Amazon Ads API v3 operations and requires node. The credentials and endpoints requested are appropriate for Amazon Ads.

Instruction Scope

Instructions confine actions to reading a local credentials JSON, requesting tokens from https://api.amazon.com, and calling Amazon advertising endpoints; the script may write an output file when --out is used. Note: SKILL.md asks the user to store LWA client secret and refresh token in a plaintext file (amazon-ads-api.json), which is a sensitive practice and should be protected.

Install Mechanism

No install spec is provided (instruction-only), and the only required binary is node. Included script is self-contained and performs network calls; nothing is downloaded from external/personal URLs during install.

Credentials

The skill requests LWA client id/secret, refresh token, profileId and region—these are expected for Amazon Ads use. However, they are stored/read from a local JSON file (unprotected by default). The SKILL.md references an optional AMAZON_ADS_PATH env var but the registry metadata lists no required env vars; this mismatch is minor but worth noting.

Persistence & Privilege

The skill is not always-enabled, does not request persistent platform privileges, and does not modify other skills or agent configs. It runs on-demand (or via normal autonomous invocation) and only reads/writes the credential file and optional output file.

Assessment

This skill appears to do what it says: it uses your LWA client id/secret and refresh token to call Amazon Ads endpoints. Before installing or running it, verify the source (there's no homepage and owner is unverified), review the included script yourself, and avoid pasting long-lived secrets into shared repos. If you must use it, store amazon-ads-api.json with strict filesystem permissions (e.g., chmod 600), set AMAZON_ADS_PATH to a secure path, run the script in a sandbox or isolated environment first, and rotate credentials if you stop trusting the skill. Also consider creating an LWA app with limited permissions and short-lived credentials where possible.

Amazon Ads API Skill

Manage Amazon Sponsored Products campaigns from your OpenClaw agent — list profiles, view campaigns, check budgets, and pull performance data.

---

Setup

1. Create credentials file

{
  "lwaClientId": "amzn1.application-oa2-client.YOUR_CLIENT_ID",
  "lwaClientSecret": "YOUR_CLIENT_SECRET",
  "refreshToken": "Atzr|YOUR_REFRESH_TOKEN",
  "profileId": "YOUR_ADS_PROFILE_ID",
  "region": "eu"
}

Save as amazon-ads-api.json. Set AMAZON_ADS_PATH env var to point to it (default: ./amazon-ads-api.json).

Regions & endpoints:

• na → advertising-api.amazon.com
• eu → advertising-api-eu.amazon.com
• fe → advertising-api-fe.amazon.com

2. Get your Profile ID

node scripts/ads.js --profiles

Copy the profileId for your brand/marketplace and add it to the credentials file.

---

Scripts

ads.js — Campaigns & Summary

node scripts/ads.js --profiles                # list all advertiser profiles
node scripts/ads.js --campaigns               # list all SP campaigns
node scripts/ads.js --summary                 # active campaigns + budgets summary
node scripts/ads.js --campaigns --out c.json  # save to file

---

Credentials Schema

Field	Description
lwaClientId	Ads app client ID (separate from SP-API)
lwaClientSecret	Ads app client secret
refreshToken	LWA refresh token
profileId	Advertising profile ID (from --profiles)
region	na, eu, or fe

---

Notes

• Ads API uses a separate LWA app from SP-API — different client ID/secret
• Profile ID is required for all campaign operations
• Tokens are fetched fresh per request (no caching overhead for CLI use)
• For production/high-frequency use, add token caching

Related

• skill-amazon-spapi — Orders, inventory & listings