Amazon Ads API · KEYXE integration design
Advertising Integration Designed for Authorized Advertisers.
Amazon Ads API enables software applications to work with supported advertising campaign information and reporting under the required partner eligibility, access approvals and advertiser authorization.
Intended capabilities
What KEYXE would do with Ads API access
Capability families are indicative and verified against Amazon’s current Ads API documentation before implementation. Availability differs by ad product, marketplace and the advertiser’s entitlements.
| Capability | What it covers | Ad products | Read / write | Status |
|---|---|---|---|---|
| Campaign Reporting | Campaign-level spend, impressions, clicks, attributed sales and orders over a period | Sponsored Products, Sponsored Brands, Sponsored Display | Read | Not yet approved by Amazon |
| Targeting / Keywords | Keyword, product and audience target performance and current bids | Per ad product | Read | Not yet approved by Amazon |
| Search Terms | Query-level performance for keyword and automatic targeting | Sponsored Products, Sponsored Brands | Read | Not yet approved by Amazon |
| Sponsored Product / Brand / Display families | Each ad product reported and status-labeled separately; availability depends on entitlements | Each separately | Read | Not yet approved by Amazon |
| Account Profiles | The advertising profiles (per marketplace) the advertiser chooses to connect | All sponsored ads | Read | Not yet approved by Amazon |
| Budget Review | Budget settings and utilization analysis; advisory alerts only | Per ad product | Read | Not yet approved by Amazon |
| Future Write Actions | Bid or budget changes — only with explicit permission, preview and a person’s approval | Per ad product | Write — future, gated | Planned |
Separately scoped products. Amazon DSP, Amazon Marketing Cloud and Amazon Marketing Stream each require their own access and agreements. They are not part of KEYXE today and are not implied by Ads API access.
How we respect advertiser control
The advertiser stays in charge
- Separate authorization. Advertising access is designed to use its own Amazon consent flow, its own credentials and its own callback — distinct from SP-API.
- Profile choice. The advertiser chooses which advertising profiles to connect; KEYXE checks that each profile is accessible and in a supported region.
- Server-only credentials. Refresh tokens will be kept encrypted on KEYXE’s server and never shared with browsers, vendors or AI clients. (Designed; not built yet, because no live connection exists.)
- No unattended changes. Bids and budgets are never changed automatically. Future changes require permission and human approval.
- Revocation handled. Revoked access or inaccessible profiles are shown clearly, and associated data is deleted according to policy.
Data-use restrictions
Policy boundaries KEYXE keeps by default
Amazon Ads policies restrict disclosing advertising data to third parties. KEYXE does not sell, share or publish an advertiser’s data, and keeps it separated per advertiser.
Amazon Ads policies prohibit combining Amazon advertising data with other data sources without Amazon’s express prior written approval. Live joins between Ads data and seller (SP-API) or third-party data are therefore off in KEYXE’s design. The public demo only places synthetic datasets next to each other.
Off pending policy reviewSending real advertising data to an external AI provider would be a disclosure to a third party. It is disabled unless a review and any required approvals allow it.
Off pending policy reviewPolicy references: Amazon Ads API policies ·Amazon Ads Partner Network policies ·KEYXE Privacy Policy
Eligibility
Approval is not automatic
Amazon decides who may access the Ads API. Its published policies exclude, among others, companies operating a significant ecommerce business, demand-side advertising platforms and ad networks. Before any application, KEYXE’s operator, ALDER HARBOR IMPORTS LLC, must confirm its eligibility and describe its actual business activities accurately. A website alone does not establish eligibility or guarantee approval.
Advertiser authorization is not enabled. KEYXE shows no “connected” state and requests no Amazon credentials until an approved, tested flow exists.
See the advertising use cases.
Campaigns, targets, search terms, placements and budgets — all on synthetic data.