Amazon Database · included in every plan

All your Amazon data, already collected, in one place

Think of it as your Amazon database, already built. SellerMate ingests Amazon Ads, DSP, AMC, Seller Central and Vendor Central for every connected account, normalises it into one set of metrics, keeps it, and serves it through one API. Your BI stack reads from here instead of from five Amazon APIs.

Get your API key See what’s covered

Read-only keys, scoped to the accounts you choose. 81 tools, one call shape.

Paste this into Claude, ChatGPT or Cursor

Read https://www.sellermate.ai/api-docs first. It documents the SellerMate Public API: REST over HTTPS, X-API-Key auth, and every tool with its parameters is on that page.

Build me a nightly job that loads Amazon performance data from SellerMate into [BigQuery / Snowflake].

- Call get_user_context and loop over every Amazon account it returns
- For each account, pull yesterday with get_campaign_performance, get_targeting_performance and get_search_term_performance, walking every page (page, page_size 500, pagination.hasMore)
- Also re-pull the trailing [14] days so attributed sales that settle late are corrected
- Load into three tables keyed by account id, date and the row's own id, upserting on conflict
- Log row counts per account and alert me in Slack if an account returns zero rows

Rules:
- My key is in SELLERMATE_API_KEY. Send it as the X-API-Key header. Never hard-code it.
- On a 429, wait for Retry-After and retry. On 401 or 403, stop and tell me.

Stack: Python 3 with requests and the [google-cloud-bigquery / snowflake-connector] library, run by [Cloud Scheduler / cron] at 06:00.

A nightly warehouse feed, written by your assistant from the docs. Prefer a sheet? There’s a prompt for that.

Coverage

Five Amazon sources, one set of metrics

Each source below is collected by SellerMate and served through the same API. The plan it starts on matches the plan comparison.

Seller Central

from Pro

Retail sales and sessions per ASIN, orders, FBA inventory and returns, Search Query Performance.

get_retail_product_performanceget_orders_reportget_inventoryget_sqp_report

Vendor Central

from Pro

Ordered and shipped revenue and units per ASIN, glance views, customer returns, vendor inventory.

get_vendor_sales_performanceget_vendor_inventory

Amazon DSP

from Unlimited

DSP campaign performance and campaign inventory alongside your Sponsored Ads data.

get_dsp_performancelist_dsp_campaigns

Amazon Marketing Cloud

from Unlimited

AMC audiences, size estimates and reports: path to conversion, time to conversion, custom attribution, tentpole overlap.

list_amc_audiencesget_amc_path_to_conversionget_amc_custom_attribution

Sync and retention	Free	Pro	Unlimited	Enterprise
Sponsored Ads data	Included	Included	Included	Included
Seller Central	—	Included	Included	Included
Vendor Central	—	Included	Included	Included
Amazon DSP & AMC	—	—	Included	Included
Sponsored Ads sync	Every 3 days	Daily	Daily	Daily
Retail analytics sync	—	Daily	Daily	Daily
Hourly stream data	—	—	Included	Included
Data retention	30 days	90 days	Unlimited	Unlimited

Freshness and history

Numbers that settle the way Amazon’s do

Synced on a schedule

Sponsored Ads every 3 days on Free and daily from Pro; retail analytics daily from Pro. Force a sync when you need it now.

Hourly where it matters

Hourly stream data on Unlimited and Enterprise, for budget pacing, dayparting and intraday alerts.

Kept, not expired

30 days on Free, 90 on Pro, unlimited on Unlimited and Enterprise. Amazon’s own report windows are shorter.

Attribution: sales attributed to a click keep arriving for days afterwards. SellerMate re-pulls trailing windows so stored numbers settle rather than freeze. Keep a copy of your own and re-pull a trailing window too; the warehouse prompt above does.

Why not build on Amazon’s APIs directly

The pipeline is the project. It’s already running.

Everything on the left is real work that has nothing to do with the dashboard you wanted.

Building on Amazon’s APIs directly

Apply for Amazon Ads API access, and separately for the Selling Partner API, per client
Request reports asynchronously, poll until ready, download and parse, per ad type and marketplace
Store it yourself, because Amazon keeps a short window and a dashboard needs history
Reconcile the shapes: Sponsored Products, Brands, Display, DSP, AMC and retail all report differently
Keep it fresh and handle rate limits, retries and attribution windows that change after the fact

Building on SellerMate

One key, bound to your workspace and the accounts you choose
One call shape for every tool, with the same metric names everywhere
Data already collected and normalised across Ads, DSP, AMC, Seller Central and Vendor Central
History kept for as long as your plan retains it, unlimited on Unlimited and Enterprise
Every account in your workspace in one query

One place

Ads, DSP, AMC, Seller Central and Vendor Central, every account, one key.

Already normalised

One call shape, the same metric names across every ad type and source.

History kept

Amazon’s reports expire. SellerMate keeps 30 days on Free, 90 on Pro, and everything on Unlimited and Enterprise.

Fresh

Synced daily from Pro, with hourly stream data on Unlimited and Enterprise.

Cross-account

An agency’s whole book in one query, which Amazon’s APIs can’t do.

Where it lands

Into the tools your team already opens

There is no connector to install. A short script, written by your assistant, moves the data on a schedule.

Google Sheets

An Apps Script on a timer fills tabs from the reporting tools every morning. The simplest version, and enough for most teams.

Sheets prompt

Looker Studio

Point Looker Studio at the sheet, or at the warehouse table below. No connector to build.

Via the sheet

BigQuery or Snowflake

A nightly script upserts yesterday plus a trailing window per account. The prompt at the top of this page writes it.

Warehouse prompt

Power BI

Read from the warehouse table or the sheet. Power Query against a sheet is the fastest path to a first report.

Via the sheet

Cross-account

An agency’s whole book in one query

Amazon’s APIs are per account. SellerMate’s aren’t. get_user_context lists every account a key can see, and get_marketplace_summary takes a list of account ids, so one call returns totals across all of them. Every reporting tool takes an account id, so looping the rest is one line.

A key can also be limited to one client’s accounts when that is what you want.

Governance

Read-only by default

Keys scoped to accounts and to tools:read, so a BI key can never change a bid.
Every call logged against the key that made it, in the same audit log as the app.
120 requests a minute per key, with a Retry-After header. No per-call pricing.
Advertising and retail performance data only; no customer PII is served.

R is all a data feed needs. Raw spec: openapi.json.

FAQ

What analysts ask

Building something custom instead? The Developer API page is written for that.

Do I still need my own data warehouse?

Only for two reasons: joining Amazon data with data from outside Amazon, or keeping history beyond what your plan retains. For dashboards, alerts and reports that read current Amazon numbers, calling the API is enough.

How far back does the history go?

Data retention is 30 days on Free, 90 days on Pro, and unlimited on Unlimited and Enterprise. If you need history beyond your plan’s window, a nightly warehouse feed keeps your own copy.

How fresh is it?

Sponsored Ads data syncs every 3 days on Free and daily from Pro. Retail analytics syncs daily from Pro. Hourly stream data is available on Unlimited and Enterprise. A force sync is available on every plan, with a higher allowance on higher plans.

What about attribution changing after the fact?

Attributed sales keep arriving for days after a click, so the number for Tuesday is not final on Tuesday. SellerMate re-pulls trailing windows so stored numbers settle the way Amazon’s do. If you keep your own copy, re-pull a trailing window too; the warehouse prompt does.

Does it cover Vendor Central and DSP?

Vendor Central sales and inventory from Pro. Amazon DSP and Amazon Marketing Cloud from Unlimited. Vendor traffic is glance views only; sessions and conversion are not available for vendor accounts, and purchase-order data is not available.

Can I pull every client account in one call?

Yes. get_user_context lists every account your key can see, and get_marketplace_summary takes a list of account ids, so an agency’s whole book comes back in one query. Amazon’s own APIs are per account.

Is the API included in my plan?

Yes, on every plan including Free. What each plan changes is which sources are connected, how often they sync and how long data is retained, exactly as in the plan comparison on the pricing page.

Can I limit a key to one client, or to read only?

Both. A key can be read-only and restricted to specific Amazon accounts, and revoked at any time. Every call is logged against the key that made it.

Your Amazon data is one key away

Create a read-only key, paste the prompt, and the first table lands tonight.

Get your API key Not a customer yet? Book a demo