Amazon

Seller, Vendor, Ads, DSP and AMC under one key, with every data set, its status and its freshness.

On this page

Live
AmazonReads ✓ · Writes ✓

Every Amazon account you run, under one key. History is kept from the day you connect. Reads are on for every account; writes exist on Amazon only, with guardrails.

Account types

AccountWho it is forWhat you grantAccess
Seller CentralBrands selling on AmazonOrders, stock, returnsRead
Vendor CentralBrands Amazon buys fromSales, inventory, POsRead
AdsAnyone running Sponsored adsCampaigns, reportsRead; writes opt-in
DSPTeams buying programmatic displayCampaign resultsRead
AMCAdvertisers with an AMC instanceQueries, audiencesRead

Connect Amazon

About ten minutes.

  1. Sign in with Amazon

    Ads: read campaigns and reports. Changes stay off until you turn them on.

  2. Add Seller or Vendor Central

    Orders, stock, returns and sales: read only.

  3. Pick accounts, get data

    A 60-day backfill starts, then history is kept. DSP and AMC join from the same screen.

Placeholder Fails a strict build (DOCS_STRICT=1).

To write: screenshots of the three console screens, and the exact permissions each Amazon consent screen asks for

Data you get

Every data set with its status. Live means it is in your key now. Needs Brand Registry means Amazon gives it only to enrolled brands. Not available means Amazon does not share it.

DataStatusFreshnessHistory
Ads
Campaigns and ad groupsLivehourlyBackfill 60 d, then kept
Targets and keywordsLivehourlyBackfill 60 d, then kept
Search termsLivedailyBackfill 60 d, then kept past Amazon’s window
PlacementsLivehourlyBackfill 60 d, then kept
Advertised productsLivehourlyBackfill 60 d, then kept
Search terms from before you connectedNot available—Only what Amazon still holds
Seller
Orders and unitsLiveevery 15 minKept from connect
Inventory and inboundLiveevery 15 minKept from connect
FBA customer returnsLivedailyKept from connect
Catalog and listingsLivedailyKept from connect
Fees and settlementsLivedailyKept from connect
Buyer names and addressesNot available—Never shared by Amazon
Vendor
Sales performanceLivedailyKept from connect
Inventory by ASINLivedailyKept from connect
Rapid Retail Analytics: near-real-time sales and stockLivehourlyKept from connect
Purchase ordersLivedailyKept from connect
Brand
Search Query PerformanceNeeds Brand RegistryweeklyWeekly snapshots kept
Search Catalog PerformanceNeeds Brand RegistryweeklyWeekly snapshots kept
Brand Analytics: search terms, market basket, repeat purchaseNeeds Brand RegistryweeklyWeekly snapshots kept
Other brands’ sales and adsNot available—Not shared by Amazon
DSP
Campaign and line-item resultsLivedailyKept from connect
Orders and conversionsLivedailyKept from connect
AMC
Path to conversionLiveon requestKept from connect
Time to conversion and attributionLiveon requestKept from connect
Audiences: size and createLiveon requestKept from connect

Read tools

get_campaign_performance
POSThttps://build-api.sellermate.ai/v1/tools/get_campaign_performance

Spend, clicks, orders, sales and ACoS for each campaign.

ReadsAmazonGoogle Ads
get_search_term_performance
POSThttps://build-api.sellermate.ai/v1/tools/get_search_term_performance

Search terms with clicks, spend and orders, kept past Amazon's window.

ReadsAmazonGoogle Ads
get_orders_report
POSThttps://build-api.sellermate.ai/v1/tools/get_orders_report

Orders and units for a Seller account.

ReadsAmazon
get_inventory
POSThttps://build-api.sellermate.ai/v1/tools/get_inventory

Stock and inbound units.

ReadsAmazon
Placeholder Fails a strict build (DOCS_STRICT=1).

To write: which data sets in the table each read tool returns, per account type (Seller, Vendor, Ads, DSP, AMC), and any read tool still to add to the API reference

Write tools and guardrails

update_target
POSThttps://build-api.sellermate.ai/v1/tools/update_target

Change a target, behind caps, a dry run and undo.

Writes · Amazon onlyAmazon
  • Caps. Nothing moves past your limit.
  • Dry run. See it before it is applied.
  • Undo for 24 hours. Roll back in one step.
  • Audit log. Who, what, when, why.

The full rules are in Writes and guardrails.

Derived metrics

Placeholder Fails a strict build (DOCS_STRICT=1).

To write: the derived metrics Build computes (ACoS, TACoS, contribution margin per SKU, days of stock) with the formula and the inputs of each

Freshness

DataFreshnessHistoryStatus
Campaigns and ad groupshourlyBackfill 60 d, then keptLive
Targets and keywordshourlyBackfill 60 d, then keptLive
Search termsdailyBackfill 60 d, then kept past Amazon’s windowLive
PlacementshourlyBackfill 60 d, then keptLive
Advertised productshourlyBackfill 60 d, then keptLive
Search terms from before you connected—Only what Amazon still holdsNot available
Orders and unitsevery 15 minKept from connectLive
Inventory and inboundevery 15 minKept from connectLive
FBA customer returnsdailyKept from connectLive
Catalog and listingsdailyKept from connectLive
Fees and settlementsdailyKept from connectLive
Buyer names and addresses—Never shared by AmazonNot available
Sales performancedailyKept from connectLive
Inventory by ASINdailyKept from connectLive
Rapid Retail Analytics: near-real-time sales and stockhourlyKept from connectLive
Purchase ordersdailyKept from connectLive
Search Query PerformanceweeklyWeekly snapshots keptNeeds Brand Registry
Search Catalog PerformanceweeklyWeekly snapshots keptNeeds Brand Registry
Brand Analytics: search terms, market basket, repeat purchaseweeklyWeekly snapshots keptNeeds Brand Registry
Other brands’ sales and ads—Not shared by AmazonNot available
Campaign and line-item resultsdailyKept from connectLive
Orders and conversionsdailyKept from connectLive
Path to conversionon requestKept from connectLive
Time to conversion and attributionon requestKept from connectLive
Audiences: size and createon requestKept from connectLive

Amazon sales keep moving for up to 14 days. Build re-pulls those days until they settle (to confirm).

Limits and caveats

Amazon's limitWhat Build does
Search-term reports keep about 60 to 95 days, depending on the report.Build keeps them from day one.
SQP and Brand Analytics need Brand Registry.The status says so. No silent empty tables.
On a stock-out Amazon pauses only Sponsored Products.One automation on Build pauses Brands and Display too. You can build it on the API.
Vendor reports lag about 48 hours.Rapid Retail Analytics gives near-real-time vendor sales and stock.

What is not available: buyer names, other brands' sales and ads, and search terms Amazon dropped before you connected. When you disconnect, your data is held for 30 days, then deleted.

Five example calls

1. Last week's campaigns

curl -X POST https://build-api.sellermate.ai/v1/tools/get_campaign_performance \
-H "X-API-Key: $BUILD_API_KEY" \
-H "Content-Type: application/json" \
-d '{"account":"amz_northwind","start":"2026-10-22","end":"2026-10-28"}'

2. Stock by SKU

curl -X POST https://build-api.sellermate.ai/v1/tools/get_inventory \
-H "X-API-Key: $BUILD_API_KEY" \
-H "Content-Type: application/json" \
-d '{"account":"amz_northwind"}'

3. Search terms past Amazon's window

Placeholder Fails a strict build (DOCS_STRICT=1).

To write: a get_search_term_performance call for a range older than 95 days, and a sample row

4. Orders and units

Placeholder Fails a strict build (DOCS_STRICT=1).

To write: a get_orders_report call for one week, and a sample row

5. A change with a dry run

Placeholder Fails a strict build (DOCS_STRICT=1).

To write: an update_target dry run and then the applied call, with the real field names

What the official connectors can't do

Placeholder Fails a strict build (DOCS_STRICT=1).

To write: what Amazon's own tools cannot do that Build does: history past the platform window, one key across accounts, the same fields on other platforms, and guarded writes. Compare plainly and name no competitor claims you cannot back

Changelog

Changes to Amazon on Build are listed in the changelog.

Last updated 30 Oct 2026