# Build by SellerMate > Build by SellerMate is one API for marketplace and ad data. One key reads Amazon and Google Ads in the same field names, and changes campaigns on Amazon behind guardrails. Call shape (v1): POST https://build-api.sellermate.ai/v1/tools/{name} with an X-API-Key header and a JSON body. Writes exist on Amazon only; never call a write tool for another platform. Every platform answers under the same field names. Check https://build.sellermate.ai/openapi.json for tool names, never guess one. Amazon and Google Ads are live. Walmart, Flipkart, TikTok Shop and Meta Ads are coming soon. Key prefixes: sm_live_ for live keys and sm_test_ for the read-only sandbox key. Set the key in the BUILD_API_KEY environment variable. Rate limits: 60/min on Free and Build, 300/min on Scale. Data retention: Free 90 days, Build 12 months, Scale 3 years. Pricing is per connected account per month. Free: $0, 1 account; Build: $97/mo, up to 3 accounts; Scale: $500/mo, 10 included, then $33 each. Annual is 20% off on Build and Scale. Writes are on every plan, on Amazon only, with guardrails: caps on bids and budgets, a dry run, idempotency keys, undo for 24 hours and an audit log. See also https://build.sellermate.ai/SKILL.md, https://build.sellermate.ai/llms.txt and https://build.sellermate.ai/openapi.json. --- # What Build is Source: https://build.sellermate.ai/docs/get-started/what-build-is Build is one API for marketplace and ad data, with the same call shape and field names on every platform. - Amazon: Reads: yes · Writes: yes - Google Ads: Reads: yes · Writes: no > **Before you start** > > You need a Build account. The Free plan has one account and a sandbox key on demo data. ## What it is Build connects the marketplace and ad accounts you already have and answers questions about them over one API. You send one `POST` to a tool, with one key, and get rows back in the same fields whichever platform the account is on. Amazon and Google Ads are live. Other platforms follow the same call shape when they launch. ## Make your first call 1. **Get a key** Open Keys in the console, name the key, and choose what it can reach. 2. **Keep it in your tool's secrets** Store it as `BUILD_API_KEY`, so your prompts and code never contain the key itself. 3. **POST to a tool** The tool name is in the path. The body names the account and the dates. **curl** ```bash 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":"acct_123"}' ``` **Node** ```js const res = await fetch("https://build-api.sellermate.ai/v1/tools/get_inventory", { method: "POST", headers: { "X-API-Key": process.env.BUILD_API_KEY, "Content-Type": "application/json" }, body: JSON.stringify({ account: "acct_123" }), }); console.log(await res.json()); ``` **Python** ```python import os, requests res = requests.post( "https://build-api.sellermate.ai/v1/tools/get_inventory", headers={"X-API-Key": os.environ["BUILD_API_KEY"]}, json={"account": "acct_123"}, ) print(res.json()) ``` The call shape is illustrative until the contract is final. The sandbox key returns demo data and is read-only. ## What you send | Name | Type | Required | Description | |---|---|---|---| | `account` | string | yes | The account to read. A key only reaches the accounts you chose when you created it. | | `start` | date | no | First day, as `YYYY-MM-DD`. For tools that report over a period. | | `end` | date | no | Last day, as `YYYY-MM-DD`. | > **Amazon only: Writes run on Amazon accounts only** > > Changes to an Amazon account sit behind caps, a dry run and undo. Every other platform is read-only. ## What comes next _To write: a screenshot of the console Keys screen, a short list of what the Free plan includes, and the link to Get a key_ ## Questions ### Can Build change things in my accounts? On Amazon accounts only, with caps, a dry run and undo. Google Ads and the platforms that follow are read-only. ### Which platforms are live? Amazon and Google Ads. Walmart, Flipkart, TikTok Shop and Meta Ads are coming soon. ### Do I need an SDK? No. Each tool is one `POST` with a JSON body, so curl, a fetch call or your AI tool's HTTP step all work. --- # Get a key Source: https://build.sellermate.ai/docs/get-started/get-a-key Create a Build account, choose what a key can reach, and keep it in your tool's secrets. > **No account connected yet?** > > The sandbox key works before you connect anything. It is read-only and returns demo data in the same shape as a live key. ## Before you start You need a Build account. The Free plan has one account and a sandbox key. Keys come in two kinds: `sm_live_…` for your connected accounts and `sm_test_…` for the sandbox. ## Create a key 1. **Sign in to the console** Open the [console](https://build.sellermate.ai/console) and sign in. A new workspace starts on the Free plan. 2. **Connect an account** Connect Amazon or Google Ads from the console. Skip this step if you only want the sandbox key. 3. **Open Keys and name the key** Name it after what will use it, for example `monday-report`. 4. **Choose what it can reach** Pick the accounts the key may read, and whether it is read, or read and write. Writes exist on Amazon only. 5. **Copy it into your tool's secrets** Store it as `BUILD_API_KEY`. Your prompts and code then never contain the key itself. _To write: screenshots: the console Keys screen, the new-key dialog with the account and scope choices, and where the sandbox key is shown. Say whether the key is shown once._ ## Use the sandbox key The console quickstart shows the sandbox key. It is read-only and returns demo data, so you can build before you connect an account. ## Keep the key safe - Keep it in your tool's secrets, never in page code or in a prompt. - Give each tool or client its own key, so you can revoke one without touching the rest. - Choose read unless the tool needs to change an Amazon account. Scopes, revoking and rotation are in [Keys and scopes](https://build.sellermate.ai/docs/guides/keys-and-scopes.md). ## Next steps - [First call in 60 seconds](https://build.sellermate.ai/docs/get-started/first-call.md): Send a request with your key and read the answer. - [Build with your AI](https://build.sellermate.ai/docs/build-with-your-ai/claude-code.md): Paste a prompt and let your AI tool write the code. --- # First call in 60 seconds Source: https://build.sellermate.ai/docs/get-started/first-call Make a first real call to Build with the sandbox key or your own, and read the answer. > **Short on time** > > Use the sandbox key from the console quickstart. It is read-only and returns demo data. ## Before you start - A Build account and a key. The sandbox key is enough; see [Get a key](https://build.sellermate.ai/docs/get-started/get-a-key.md). - Your key in an environment variable named `BUILD_API_KEY`. - One tool to call. This page uses `get_campaign_performance`. ## Send the request One `POST` to the tool, the key in the `X-API-Key` header, and a JSON body with the account and the dates. **curl** ```bash 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":"acct_123","start":"2026-10-01","end":"2026-10-28"}' ``` **Node** ```js const res = await fetch("https://build-api.sellermate.ai/v1/tools/get_campaign_performance", { method: "POST", headers: { "X-API-Key": process.env.BUILD_API_KEY, "Content-Type": "application/json" }, body: JSON.stringify({ account: "acct_123", start: "2026-10-01", end: "2026-10-28" }), }); console.log(await res.json()); ``` **Python** ```python import os, requests res = requests.post( "https://build-api.sellermate.ai/v1/tools/get_campaign_performance", headers={"X-API-Key": os.environ["BUILD_API_KEY"]}, json={"account": "acct_123", "start": "2026-10-01", "end": "2026-10-28"}, ) print(res.json()) ``` The call shape is illustrative until the contract is final. ## Read the answer Every row has the same fields on Amazon and Google Ads. An answer looks like this: **Response** ```json { "rows": [ { "platform": "amazon", "account_id": "amz_northwind", "campaign_name": "SP - Bottles - Exact", "spend": 1842.10, "clicks": 2210, "orders": 161, "sales": 6120.40, "acos": 0.301, "currency": "USD" } ], "meta": { "data_as_of": "2026-10-30T06:00:00Z" } } ``` `data_as_of` says how fresh the answer is. Amazon sales keep moving for up to 14 days, and Build re-pulls those days until they settle. _To write: replace the sample with a real sandbox response: the exact envelope (where data_as_of and settling_from sit), real field types, and one real row_ ## If it fails A `429` means you went over the plan's requests per minute. The body says when to retry: ```json { "error": "rate_limited", "retry": 12, "upgrade": "https://build.sellermate.ai/pricing" } ``` Wait that many seconds and send it again. Limits per plan are in [Plans and limits](https://build.sellermate.ai/docs/guides/plans-and-limits.md). _To write: one more common error and its fix, for example a missing or wrong key, with the real status and body_ ## Next steps - [Build with your AI](https://build.sellermate.ai/docs/build-with-your-ai/claude-code.md): Let your AI tool write the code for you. - [API reference](https://build.sellermate.ai/docs/api-reference/overview.md): Every tool, its fields and its errors. --- # Claude Code Source: https://build.sellermate.ai/docs/build-with-your-ai/claude-code Point Claude Code at the Build docs and your key, paste one sentence, and let it write the call. Use Claude Code for: a file or an analysis. It reads the same docs as every other tool. ## Where the key goes Export the key in the shell Claude Code runs in, or keep it in a `.env` file that is not committed. The key is always named `BUILD_API_KEY`, and the prompt names the variable, never the key. _To write: the exact steps and a screenshot for putting BUILD_API_KEY into Claude Code_ ## The prompt Paste this into Claude Code. It points your AI at the docs and at your key, then says what you want. Prompt for claude-code: ``` Read https://build.sellermate.ai/SKILL.md. My key is in BUILD_API_KEY. Rank all my clients by ACoS drift, spend spike and sales drop since last week, worst first. ``` ## A worked example _To write: a worked example in Claude Code: the prompt, what Claude Code writes, the call it makes to Build, and what you check before you run it_ ## Expected output The example above should end with: 5 clients ranked, Kettle Lane first. _To write: a screenshot or sample of the real output for this prompt_ ## If it breaks Paste the error back into Claude Code. Errors say what to change, and a `429` says when to retry. Reads are safe to run again. --- # Cursor Source: https://build.sellermate.ai/docs/build-with-your-ai/cursor Point Cursor at the Build docs and your key, paste one sentence, and let it write the call. Use Cursor for: a file or an analysis. It reads the same docs as every other tool. ## Where the key goes Keep the key in an environment variable or a `.env` file that is not committed, never in a file Cursor writes into your repo. The key is always named `BUILD_API_KEY`, and the prompt names the variable, never the key. _To write: the exact steps and a screenshot for putting BUILD_API_KEY into Cursor_ ## The prompt Paste this into Cursor. It points your AI at the docs and at your key, then says what you want. Prompt for cursor: ``` Read https://build.sellermate.ai/SKILL.md. My key is in BUILD_API_KEY. Export last month’s sales, fees, refunds and ad spend by SKU as one CSV for my bookkeeper. ``` ## A worked example _To write: a worked example in Cursor: the prompt, what Cursor writes, the call it makes to Build, and what you check before you run it_ ## Expected output The example above should end with: october-close.csv saved. _To write: a screenshot or sample of the real output for this prompt_ ## If it breaks Paste the error back into Cursor. Errors say what to change, and a `429` says when to retry. Reads are safe to run again. --- # Lovable Source: https://build.sellermate.ai/docs/build-with-your-ai/lovable Point Lovable at the Build docs and your key, paste one sentence, and let it write the call. Use Lovable for: a page or an app. It reads the same docs as every other tool. ## Where the key goes Save the key as a secret in Lovable, never in page code. The prompt says the key is saved as a secret. The key is always named `BUILD_API_KEY`, and the prompt names the variable, never the key. _To write: the exact steps and a screenshot for putting BUILD_API_KEY into Lovable_ ## The prompt Paste this into Lovable. It points your AI at the docs and at your key, then says what you want. Prompt for lovable: ``` Read https://build.sellermate.ai/SKILL.md. My key is in BUILD_API_KEY, saved as a secret. Build me a page with profit per SKU after fees, returns and ad spend, red when below zero. ``` ## A worked example _To write: a worked example in Lovable: the prompt, what Lovable writes, the call it makes to Build, and what you check before you run it_ ## Expected output The example above should end with: profit page live, KB-077 in red. _To write: a screenshot or sample of the real output for this prompt_ ## If it breaks Paste the error back into Lovable. Errors say what to change, and a `429` says when to retry. Reads are safe to run again. --- # n8n Source: https://build.sellermate.ai/docs/build-with-your-ai/n8n Point n8n at the Build docs and your key, paste one sentence, and let it write the call. Use n8n for: something on a schedule. It reads the same docs as every other tool. ## Where the key goes Store the key in an n8n credential and add it to the HTTP Request node as the `X-API-Key` header. The key is always named `BUILD_API_KEY`, and the prompt names the variable, never the key. _To write: the exact steps and a screenshot for putting BUILD_API_KEY into n8n_ ## The prompt Paste this into n8n. It points your AI at the docs and at your key, then says what you want. Prompt for n8n: ``` Read https://build.sellermate.ai/SKILL.md. My key is in BUILD_API_KEY. Every Monday at 8, post each client’s spend, sales, ACoS and change vs last week to our team channel. ``` ## A worked example _To write: a worked example in n8n: the prompt, what n8n writes, the call it makes to Build, and what you check before you run it_ ## Expected output The example above should end with: Monday cards in #client-reports. _To write: a screenshot or sample of the real output for this prompt_ ## If it breaks Paste the error back into n8n. Errors say what to change, and a `429` says when to retry. Reads are safe to run again. --- # Zapier Source: https://build.sellermate.ai/docs/build-with-your-ai/zapier Point Zapier at the Build docs and your key, paste one sentence, and let it write the call. Use Zapier for: something on a schedule. It reads the same docs as every other tool. ## Where the key goes Keep the key in the Zap step that calls Build, as the `X-API-Key` header, and not in a field that is shared. The key is always named `BUILD_API_KEY`, and the prompt names the variable, never the key. _To write: the exact steps and a screenshot for putting BUILD_API_KEY into Zapier_ ## The prompt Paste this into Zapier. It points your AI at the docs and at your key, then says what you want. Prompt for zapier: ``` Read https://build.sellermate.ai/SKILL.md. My key is in BUILD_API_KEY. Email me every Monday revenue, ad spend and TACoS, Amazon and Google Ads side by side. ``` ## A worked example _To write: a worked example in Zapier: the prompt, what Zapier writes, the call it makes to Build, and what you check before you run it_ ## Expected output The example above should end with: Monday email scheduled. _To write: a screenshot or sample of the real output for this prompt_ ## If it breaks Paste the error back into Zapier. Errors say what to change, and a `429` says when to retry. Reads are safe to run again. --- # Amazon Source: https://build.sellermate.ai/docs/platforms/amazon Seller, Vendor, Ads, DSP and AMC under one key, with every data set, its status and its freshness. Status: Live - Amazon: Reads: yes · Writes: yes 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 | Account | Who it is for | What you grant | Access | |---|---|---|---| | Seller Central | Brands selling on Amazon | Orders, stock, returns | Read | | Vendor Central | Brands Amazon buys from | Sales, inventory, POs | Read | | Ads | Anyone running Sponsored ads | Campaigns, reports | Read; writes opt-in | | DSP | Teams buying programmatic display | Campaign results | Read | | AMC | Advertisers with an AMC instance | Queries, audiences | Read | ## 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. _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. **Ads** | Data | Status | Freshness | History | |---|---|---|---| | Campaigns and ad groups | Live | hourly | Backfill 60 d, then kept | | Targets and keywords | Live | hourly | Backfill 60 d, then kept | | Search terms | Live | daily | Backfill 60 d, then kept past Amazon’s window | | Placements | Live | hourly | Backfill 60 d, then kept | | Advertised products | Live | hourly | Backfill 60 d, then kept | | Search terms from before you connected | Not available | — | Only what Amazon still holds | **Seller** | Data | Status | Freshness | History | |---|---|---|---| | Orders and units | Live | every 15 min | Kept from connect | | Inventory and inbound | Live | every 15 min | Kept from connect | | FBA customer returns | Live | daily | Kept from connect | | Catalog and listings | Live | daily | Kept from connect | | Fees and settlements | Live | daily | Kept from connect | | Buyer names and addresses | Not available | — | Never shared by Amazon | **Vendor** | Data | Status | Freshness | History | |---|---|---|---| | Sales performance | Live | daily | Kept from connect | | Inventory by ASIN | Live | daily | Kept from connect | | Rapid Retail Analytics: near-real-time sales and stock | Live | hourly | Kept from connect | | Purchase orders | Live | daily | Kept from connect | **Brand** | Data | Status | Freshness | History | |---|---|---|---| | Search Query Performance | Needs Brand Registry | weekly | Weekly snapshots kept | | Search Catalog Performance | Needs Brand Registry | weekly | Weekly snapshots kept | | Brand Analytics: search terms, market basket, repeat purchase | Needs Brand Registry | weekly | Weekly snapshots kept | | Other brands’ sales and ads | Not available | — | Not shared by Amazon | **DSP** | Data | Status | Freshness | History | |---|---|---|---| | Campaign and line-item results | Live | daily | Kept from connect | | Orders and conversions | Live | daily | Kept from connect | **AMC** | Data | Status | Freshness | History | |---|---|---|---| | Path to conversion | Live | on request | Kept from connect | | Time to conversion and attribution | Live | on request | Kept from connect | | Audiences: size and create | Live | on request | Kept from connect | ## Read tools POST https://build-api.sellermate.ai/v1/tools/get_campaign_performance — Spend, clicks, orders, sales and ACoS for each campaign. (writes: no; platforms: Amazon, Google Ads) POST https://build-api.sellermate.ai/v1/tools/get_search_term_performance — Search terms with clicks, spend and orders, kept past Amazon's window. (writes: no; platforms: Amazon, Google Ads) POST https://build-api.sellermate.ai/v1/tools/get_orders_report — Orders and units for a Seller account. (writes: no; platforms: Amazon) POST https://build-api.sellermate.ai/v1/tools/get_inventory — Stock and inbound units. (writes: no; platforms: Amazon) _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 > **Amazon only: Writes run on Amazon accounts only** > > You can change bids, budgets, negatives and campaigns. Changes stay off until you turn them on, and a key needs the read and write scope. POST https://build-api.sellermate.ai/v1/tools/update_target — Change a target, behind caps, a dry run and undo. (writes: yes; platforms: Amazon) - **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](https://build.sellermate.ai/docs/guides/writes-and-guardrails.md). ## Derived metrics _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 > **Freshness figures (to confirm)** > > The figures below, and "Amazon sales move for up to 14 days", are the current site statements. Each is (to confirm) before launch. Every answer carries `data_as_of`. | Data | Freshness | History | Status | |---|---|---|---| | Campaigns and ad groups | hourly | Backfill 60 d, then kept | Live | | Targets and keywords | hourly | Backfill 60 d, then kept | Live | | Search terms | daily | Backfill 60 d, then kept past Amazon’s window | Live | | Placements | hourly | Backfill 60 d, then kept | Live | | Advertised products | hourly | Backfill 60 d, then kept | Live | | Search terms from before you connected | — | Only what Amazon still holds | Not available | | Orders and units | every 15 min | Kept from connect | Live | | Inventory and inbound | every 15 min | Kept from connect | Live | | FBA customer returns | daily | Kept from connect | Live | | Catalog and listings | daily | Kept from connect | Live | | Fees and settlements | daily | Kept from connect | Live | | Buyer names and addresses | — | Never shared by Amazon | Not available | | Sales performance | daily | Kept from connect | Live | | Inventory by ASIN | daily | Kept from connect | Live | | Rapid Retail Analytics: near-real-time sales and stock | hourly | Kept from connect | Live | | Purchase orders | daily | Kept from connect | Live | | Search Query Performance | weekly | Weekly snapshots kept | Needs Brand Registry | | Search Catalog Performance | weekly | Weekly snapshots kept | Needs Brand Registry | | Brand Analytics: search terms, market basket, repeat purchase | weekly | Weekly snapshots kept | Needs Brand Registry | | Other brands’ sales and ads | — | Not shared by Amazon | Not available | | Campaign and line-item results | daily | Kept from connect | Live | | Orders and conversions | daily | Kept from connect | Live | | Path to conversion | on request | Kept from connect | Live | | Time to conversion and attribution | on request | Kept from connect | Live | | Audiences: size and create | on request | Kept from connect | Live | Amazon sales keep moving for up to 14 days. Build re-pulls those days until they settle (to confirm). ## Limits and caveats | Amazon's limit | What 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** ```bash 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** ```bash 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 _To write: a get_search_term_performance call for a range older than 95 days, and a sample row_ ### 4. Orders and units _To write: a get_orders_report call for one week, and a sample row_ ### 5. A change with a dry run _To write: an update_target dry run and then the applied call, with the real field names_ ## What the official connectors can't do _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](https://build.sellermate.ai/docs/changelog.md). --- # Google Ads Source: https://build.sellermate.ai/docs/platforms/google-ads Client and manager accounts under one consent, read-only, with campaigns, search terms and conversions next to your Amazon numbers. Status: Live - Google Ads: Reads: yes · Writes: no Every campaign, search term and conversion, next to your Amazon numbers, under the same field names. Build holds the developer token, so you never apply to Google. ## Account types | Account | Who it is for | What you grant | |---|---|---| | Client account | Anyone running ads in their own Google Ads account | Sign in with Google and approve view-only access | | Manager account (MCC) | Agencies and brands with several accounts | One approval on the manager covers every client under it | ## Connect Google Ads A few minutes. 1. **Sign in with Google** Approve view-only access. For a manager account, one approval covers every client under it. 2. **Pick your accounts** Choose the client accounts Build should read. 3. **First data lands** It takes minutes. Every row carries its as-of time. _To write: screenshots of the three console screens, and the exact permission the Google consent screen shows_ ## Data you get Every row says what it is. Some Google data is hidden or restated, and the status says which. **Campaigns** | Data | Status | Freshness | History | |---|---|---|---| | Spend, clicks, conversions by campaign | Live | hourly | Kept from day one | | Budgets and bidding strategies | Live | daily | Every change kept | | Auction insights (competitor share) | Not available | — | Google doesn’t share it | **Ad groups and ads** | Data | Status | Freshness | History | |---|---|---|---| | Ad group results | Live | hourly | Kept from day one | | Ads, headlines and their results | Live | hourly | Kept from day one | **Keywords and search terms** | Data | Status | Freshness | History | |---|---|---|---| | Keywords and Quality Score | Live | daily | Kept from day one | | Search terms Google shows | Live | daily | Kept from day one | | Low-volume search terms | Hidden by Google | — | Spend gap shown | | Who searched (person-level data) | Not available | — | Google doesn’t share it | **Shopping and Performance Max products** | Data | Status | Freshness | History | |---|---|---|---| | Shopping results by product | Live | daily | Kept from day one | | Performance Max results by product | Live | daily | Kept from day one | | Performance Max search terms | Hidden by Google | — | Categories only | **Conversions** | Data | Status | Freshness | History | |---|---|---|---| | Conversions and value by day | Live | hourly | Every restated value kept | | Conversions by action | Live | daily | Every restated value kept | **Geo and device** | Data | Status | Freshness | History | |---|---|---|---| | Results by country, region and city | Live | daily | Kept from day one | | Results by device and hour of day | Live | daily | Kept from day one | ## Read tools POST https://build-api.sellermate.ai/v1/tools/get_campaign_performance — Spend, clicks, orders, sales and ACoS for each campaign, in the same fields as Amazon. (writes: no; platforms: Amazon, Google Ads) POST https://build-api.sellermate.ai/v1/tools/get_search_term_performance — Search terms with their performance, hidden terms marked. (writes: no; platforms: Amazon, Google Ads) _To write: which data groups in the table each read tool returns, and any Google Ads read tool still to add to the API reference (conversions, geo and device, Shopping and Performance Max)_ ## Write tools and guardrails > **Read-only for now** > > Build never changes your Google Ads account. Writes come later. Amazon is the only platform with writes today. | Google Ads | Today | |---|---| | Read campaigns and budgets | Yes | | Read search terms and conversions | Yes | | Change bids or budgets | No | | Pause campaigns or add negatives | No | ## Derived metrics _To write: the derived metrics on Google Ads (ACoS and TACoS blended with Amazon, brand and non-brand split, conversion lag) with the formula and the inputs of each_ ## Freshness > **Freshness figures (to confirm)** > > The figures below are the current site statements. Each is (to confirm) before launch. Past days are re-pulled when Google restates them. Every answer carries `data_as_of`. | Data | Freshness | History | Status | |---|---|---|---| | Spend, clicks, conversions by campaign | hourly | Kept from day one | Live | | Budgets and bidding strategies | daily | Every change kept | Live | | Auction insights (competitor share) | — | Google doesn’t share it | Not available | | Ad group results | hourly | Kept from day one | Live | | Ads, headlines and their results | hourly | Kept from day one | Live | | Keywords and Quality Score | daily | Kept from day one | Live | | Search terms Google shows | daily | Kept from day one | Live | | Low-volume search terms | — | Spend gap shown | Hidden by Google | | Who searched (person-level data) | — | Google doesn’t share it | Not available | | Shopping results by product | daily | Kept from day one | Live | | Performance Max results by product | daily | Kept from day one | Live | | Performance Max search terms | — | Categories only | Hidden by Google | | Conversions and value by day | hourly | Every restated value kept | Live | | Conversions by action | daily | Every restated value kept | Live | | Results by country, region and city | daily | Kept from day one | Live | | Results by device and hour of day | daily | Kept from day one | Live | ## Limits and caveats | Google's limit | What Build does | |---|---| | API access comes in tiers, and approval takes days. | Build already holds the token. You never apply. | | The search-term report hides low-volume terms. | They show as hidden by Google, with the spend behind them. | | Conversions arrive late. Past days get restated. | Build re-pulls and shows the restated value. | | Manager accounts must be linked to their clients. | One consent on the manager covers every client under it. | What is not available: auction insights and person-level data. Performance Max search terms come as categories only. When you disconnect, Build stops reading right away, and history Build already kept stays yours to delete. ## Five example calls ### 1. Last week's campaigns **curl** ```bash 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":"gads_northwind","start":"2026-10-22","end":"2026-10-28"}' ``` ### 2. Search terms that spend **curl** ```bash curl -X POST https://build-api.sellermate.ai/v1/tools/get_search_term_performance \ -H "X-API-Key: $BUILD_API_KEY" \ -H "Content-Type: application/json" \ -d '{"account":"gads_northwind","start":"2026-10-01","end":"2026-10-28"}' ``` ### 3. Amazon and Google Ads side by side _To write: two get_campaign_performance calls, one per platform, and how to join the rows on the shared field names_ ### 4. Hidden search terms _To write: how a hidden-by-Google term appears in a get_search_term_performance row, with a real sample_ ### 5. A restated day _To write: a call over a range that includes restated conversions, and how data_as_of and the restated value show_ ## What the official connectors can't do _To write: what Google's own tools cannot do that Build does: the same field names as Amazon in one call, one consent for a manager, hidden terms marked with their spend, and history. Compare plainly_ ## Changelog Changes to Google Ads on Build are listed in the [changelog](https://build.sellermate.ai/docs/changelog.md). --- # Walmart Source: https://build.sellermate.ai/docs/platforms/walmart Walmart is coming soon to Build: Marketplace orders, stock and returns, and Walmart Connect ads, under the same field names as Amazon. Status: Coming soon Status: Planned - Walmart: Coming soon Your Walmart orders, stock and ads, under the same field names as Amazon. Walmart is not live yet. It is next. No date is promised. Every platform costs the same per account. ## Planned coverage | Account | What we plan to read | How you grant access | Status | |---|---|---|---| | Marketplace | Orders, items, stock and returns. | Marketplace API keys from your Walmart seller account. | Planned | | Walmart Connect, Sponsored Search | Campaigns, keywords and items. | You enable Build as a partner in Walmart Connect. | Planned | | Walmart Connect, Display | Display campaign performance. | An onboarding case with Walmart Connect. Walmart enables it per advertiser. | Planned | ## Planned data | Area | Data | Detail | Status | |---|---|---|---| | Marketplace | Orders | Status, items, totals | Planned | | Marketplace | Items and listings | Catalog and price | Planned | | Marketplace | Inventory | Stock by item | Planned | | Marketplace | Returns | By item and reason | Planned | | Marketplace | Settlements | Payouts and fees | Researching | | Marketplace | Prices and Buy Box | Yours against the winner | Researching | | Walmart Connect | Sponsored Search | Campaigns, keywords, items | Planned | | Walmart Connect | Display | Campaign performance | Planned | | Walmart Connect | Search-term reports | What shoppers typed | Researching | Not available: Other sellers’ sales. Walmart doesn’t share them. ## Freshness > **Freshness (to confirm)** > > Walmart Connect data refreshes daily and shows the previous day (to confirm). ## Access and writes Marketplace API keys for orders and stock. For ads, you enable Build as a partner in Walmart Connect (Sponsored Search) or open an onboarding case (Display). Walmart is read-only at launch. Writes with guardrails are on Amazon only; see [Writes and guardrails](https://build.sellermate.ai/docs/guides/writes-and-guardrails.md). ## Launch and waitlist _To write: the ETA wording the CTO wants (no quarter or date unless confirmed) and where the Walmart waitlist form lives_ ## Until then The field names are the same on every platform, so a report built on Amazon and Google Ads today does not change when Walmart lands. See [Amazon](https://build.sellermate.ai/docs/platforms/amazon.md) and [Google Ads](https://build.sellermate.ai/docs/platforms/google-ads.md). --- # Flipkart Source: https://build.sellermate.ai/docs/platforms/flipkart Flipkart is planned for Build: orders, settlements, returns and stock for sellers, under the same field names as Amazon. Status: Coming soon Status: Planned - Flipkart: Coming soon Your Flipkart orders, settlements and returns, under the same field names as Amazon. Flipkart is not live yet. No date is promised. Every platform costs the same per account. ## Planned coverage | Account | What we plan to read | How you grant access | Status | |---|---|---|---| | Seller account | Orders, listings, settlements and returns. | You approve Build as an app on your Flipkart seller account. | Planned | | Fulfilment by Flipkart | Warehouse stock, stranded and unsellable units. | Read from the same seller account, where Flipkart offers it. | Planned | | Ads | Campaign results, if Flipkart opens them. | Not known yet. We are checking what Flipkart offers. | Researching | ## Planned data | Area | Data | Detail | Status | |---|---|---|---| | Seller account | Orders | Status, items, totals | Planned | | Seller account | Listings | Catalog and price | Planned | | Seller account | Settlements | Payouts and fees | Planned | | Seller account | Returns | By item and reason | Planned | | Seller account | Warehouse stock | Including stranded stock | Planned | | Seller account | Profit and loss | By period | Planned | | Flipkart ads | Ad campaigns | Campaigns and results | Researching | | Flipkart ads | Search terms | What shoppers typed | Researching | Not available: Customer names and addresses. Not part of Flipkart’s order data. ## Access and writes You approve Build as an app on your seller account. Flipkart reviews partner apps before sellers can approve them, so there is a review step on our side first. Flipkart is read-only at launch. Writes with guardrails are on Amazon only; see [Writes and guardrails](https://build.sellermate.ai/docs/guides/writes-and-guardrails.md). ## Launch and waitlist _To write: the ETA wording the CTO wants (no quarter or date unless confirmed) and where the Flipkart waitlist form lives_ ## Until then The field names are the same on every platform, so a report built on Amazon and Google Ads today does not change when Flipkart lands. See [Amazon](https://build.sellermate.ai/docs/platforms/amazon.md) and [Google Ads](https://build.sellermate.ai/docs/platforms/google-ads.md). --- # TikTok Shop Source: https://build.sellermate.ai/docs/platforms/tiktok-shop TikTok Shop is planned for Build: orders, stock, returns and creator sales under the same field names as Amazon. Status: Coming soon Status: Planned - TikTok Shop: Coming soon Your TikTok Shop orders, stock and creator sales, under the same field names as Amazon. TikTok Shop is not live yet. No date is promised. Every platform costs the same per account. ## Planned coverage | Account | What we plan to read | How you grant access | Status | |---|---|---|---| | Shop | Products, orders, stock, returns and finance. | You approve Build as an app on your shop. TikTok reviews apps before they go live. | Planned | | Affiliate | Creator collaborations, affiliate links and affiliate orders. | Not known yet. We are checking what it needs. | Researching | | TikTok Ads, ad spend | Spend and GMV Max results. | Ads may need a separate TikTok Ads approval. We are checking. | Researching | ## Planned data | Area | Data | Detail | Status | |---|---|---|---| | Shop | Orders | Status, items, totals | Planned | | Shop | Products | Catalog and price | Planned | | Shop | Inventory | Stock by item | Planned | | Shop | Fulfilment | Shipping and logistics | Planned | | Shop | Returns and refunds | By item and reason | Planned | | Shop | Finance | Payouts and fees | Planned | | Creators and ads | Affiliate orders | Creator links and orders | Researching | | Creators and ads | Ad spend and GMV Max | From TikTok Ads | Researching | Not available: Other shops’ sales. TikTok doesn’t share them. ## Access and writes You approve Build as an app on your shop. TikTok reviews apps before they go live, so there is a review step on our side first. Ads may need a separate approval in your TikTok Ads account. TikTok Shop is read-only at launch. Writes with guardrails are on Amazon only; see [Writes and guardrails](https://build.sellermate.ai/docs/guides/writes-and-guardrails.md). ## Launch and waitlist _To write: the ETA wording the CTO wants (no quarter or date unless confirmed) and where the TikTok Shop waitlist form lives_ ## Until then The field names are the same on every platform, so a report built on Amazon and Google Ads today does not change when TikTok Shop lands. See [Amazon](https://build.sellermate.ai/docs/platforms/amazon.md) and [Google Ads](https://build.sellermate.ai/docs/platforms/google-ads.md). --- # Meta Ads Source: https://build.sellermate.ai/docs/platforms/meta-ads Meta Ads is planned for Build: Facebook and Instagram spend and results next to Amazon, under the same field names. Status: Coming soon Status: Planned - Meta Ads: Coming soon Your Facebook and Instagram ads, next to Amazon, under the same field names. Meta Ads is not live yet. No date is promised. Every platform costs the same per account. ## Planned coverage | Account | What we plan to read | How you grant access | Status | |---|---|---|---| | Ad accounts | Campaigns, ad sets, ads and creatives. | You approve Build on your ad account. Meta reviews apps that read other people’s ad accounts. | Planned | | Insights | Spend, results and ROAS, with breakdowns. | Covered by the same approval. | Planned | | Catalogs | Product catalogs for Shopping ads. | Not known yet. We are checking what it needs. | Researching | ## Planned data | Area | Data | Detail | Status | |---|---|---|---| | Ad accounts | Campaigns, ad sets, ads | Structure and status | Planned | | Ad accounts | Creatives | What each ad shows | Planned | | Ad accounts | Spend and results | Clicks, conversions, ROAS | Planned | | Ad accounts | Breakdowns | Placement, age, device | Planned | | Catalogs and events | Product catalogs | Feeds and health | Researching | | Catalogs and events | Conversion events | What your site sends Meta | Researching | Not available: Search terms. Meta is not a search product. ## Access and writes You approve Build on your ad account. Meta reviews apps that read other people’s ad accounts, so there is a review step on our side first. Meta Ads is read-only at launch. Writes with guardrails are on Amazon only; see [Writes and guardrails](https://build.sellermate.ai/docs/guides/writes-and-guardrails.md). ## Launch and waitlist _To write: the ETA wording the CTO wants (no quarter or date unless confirmed) and where the Meta Ads waitlist form lives_ ## Until then The field names are the same on every platform, so a report built on Amazon and Google Ads today does not change when Meta Ads lands. See [Amazon](https://build.sellermate.ai/docs/platforms/amazon.md) and [Google Ads](https://build.sellermate.ai/docs/platforms/google-ads.md). --- # Reporting Source: https://build.sellermate.ai/docs/recipes/reporting Send spend, sales and ACoS to the people who need them, on a schedule, from your AI tool. - Amazon: Reads: yes · Writes: yes ## What you get Send a report without opening a dashboard. Your AI tool asks Build for the numbers, shapes them, and posts them where your team already looks. The result is a Slack card per client, a Sheet row, an email, or a CSV, depending on the prompt below. _To write: the output mock for this recipe: a screenshot or sample of the real result, with numbers blurred_ ## The prompt Paste a prompt into your AI tool. Each one points the tool at the docs and at your key, which stays in `BUILD_API_KEY`. ### Monday client report For n8n. Schedule: Mondays at 8. Prompt for n8n: ``` Read https://build.sellermate.ai/SKILL.md. My key is in BUILD_API_KEY. Build me a weekly report of spend, sales and ACoS for every client and post it to Slack #client-reports on Mondays. ``` ### Weekly exec card For Zapier. Schedule: Mondays at 8. Prompt for zapier: ``` Read https://build.sellermate.ai/SKILL.md. My key is in BUILD_API_KEY. Build me a Zapier zap that every Monday at 8 adds up last week’s revenue, units, ad spend, TACoS and margin across all my channels and sends one card to Slack #weekly. ``` ### Month-end export For Cursor. Schedule: The 1st of each month at 7. Prompt for cursor: ``` Read https://build.sellermate.ai/SKILL.md. My key is in BUILD_API_KEY. Write me a script that on the 1st of each month pulls last month’s Amazon Seller settlements and Amazon Ads spend and saves one CSV by SKU, with sales, fees, refunds, ad spend and COGS, named like 2026-10.csv, in the folder bookkeeper. ``` ## Steps 1. **Get a key** Create a key in the console and save it as `BUILD_API_KEY` in your tool's secrets. See [Get a key](https://build.sellermate.ai/docs/get-started/get-a-key.md). 2. **Paste the prompt** Pick the prompt above for your tool and paste it. Change the names in it, such as the channel or the Sheet, to yours. 3. **Run it once** Check the first result against your own numbers before you schedule it. 4. **Schedule it** Ask your tool to run it on the schedule shown with the prompt. ## Calls it makes _To write: the sequence of Build calls this recipe makes, with one real request and response in CodeTabs_ ## Data used - [`get_campaign_performance`](https://build.sellermate.ai/docs/api-reference/get-campaign-performance.md) - [`get_orders_report`](https://build.sellermate.ai/docs/api-reference/get-orders-report.md) ## Variants Add one of these to the prompt: - Add Google Ads to the report. - Post to a different channel. - Send the CSV to your bookkeeper by email. - Only include clients over a monthly spend. --- # Wasted spend Source: https://build.sellermate.ai/docs/recipes/wasted-spend Find search terms that spend and never sell, list them every week, and add negatives after you approve. - Amazon: Reads: yes · Writes: yes ## What you get Find the search terms that take clicks and never sell. Start with a list, and move to negatives on Amazon when you trust it. The result is a Sheet of zero-sale, high-click search terms, costliest first, and, on Amazon, a dry run of proposed negatives. _To write: the output mock for this recipe: a screenshot or sample of the real result, with numbers blurred_ ## The prompt Paste a prompt into your AI tool. Each one points the tool at the docs and at your key, which stays in `BUILD_API_KEY`. ### Wasted-spend sheet For Zapier. Schedule: Mondays at 7. Prompt for zapier: ``` Read https://build.sellermate.ai/SKILL.md. My key is in BUILD_API_KEY. Build me a Zapier zap that every Monday finds Amazon Ads search terms with 15 or more clicks and no sales in the last 30 days, and adds them to the Google Sheet wasted-spend, costliest first. ``` ### Negatives sweep For Claude Code. Schedule: Mondays at 9. Prompt for claude-code: ``` Read https://build.sellermate.ai/SKILL.md. My key is in BUILD_API_KEY. Every week, find Amazon Ads search terms with 15 or more clicks and no sales, and list them as proposed negative keywords. Show me a dry run in #approvals, wait for my yes, then add only the approved ones, 50 at most, and keep a log. ``` > **Amazon only: The change step runs on Amazon accounts only** > > It needs a key with the read and write scope. It uses a dry run first, caps, a 24 hour undo and an audit log. See [Writes and guardrails](https://build.sellermate.ai/docs/guides/writes-and-guardrails.md). _To write: which tool applies the change in this recipe (negatives or an ad pause): the API reference lists update_target, and the negatives tool is not listed yet_ ## Steps 1. **Get a key** Create a key in the console and save it as `BUILD_API_KEY` in your tool's secrets. See [Get a key](https://build.sellermate.ai/docs/get-started/get-a-key.md). 2. **Paste the prompt** Pick the prompt above for your tool and paste it. Change the names in it, such as the channel or the Sheet, to yours. 3. **Run it once** Check the first result against your own numbers before you schedule it. 4. **Schedule it** Ask your tool to run it on the schedule shown with the prompt. ## Calls it makes _To write: the sequence of Build calls this recipe makes, with one real request and response in CodeTabs_ ## Data used - [`get_search_term_performance`](https://build.sellermate.ai/docs/api-reference/get-search-term-performance.md) ## Variants Add one of these to the prompt: - Use 25 clicks as the limit. - Add the campaign name to each row. - Skip terms that contain your brand name. - Only add exact negatives. --- # Launches Source: https://build.sellermate.ai/docs/recipes/launches Follow a new ASIN from sales to stock on one page that refreshes every morning. - Amazon: Reads: yes · Writes: yes ## What you get Watch a launch on one page. Paste an ASIN and see its sales, ad spend, ACoS, top search terms and stock together. The result is one shareable page per ASIN, refreshed every morning. _To write: the output mock for this recipe: a screenshot or sample of the real result, with numbers blurred_ ## The prompt Paste a prompt into your AI tool. Each one points the tool at the docs and at your key, which stays in `BUILD_API_KEY`. ### New ASIN launch page For Lovable. Schedule: Every morning at 7. Prompt for lovable: ``` Read https://build.sellermate.ai/SKILL.md. My key is in BUILD_API_KEY, saved as a secret. Build me a Lovable page where I paste an ASIN and see its sales, ad spend, ACoS, top search terms and stock in one place, using the last 30 days. Refresh it every morning and give me a link I can share. Save the pages in launch-pages. ``` ## Steps 1. **Get a key** Create a key in the console and save it as `BUILD_API_KEY` in your tool's secrets. See [Get a key](https://build.sellermate.ai/docs/get-started/get-a-key.md). 2. **Paste the prompt** Pick the prompt above for your tool and paste it. Change the names in it, such as the channel or the Sheet, to yours. 3. **Run it once** Check the first result against your own numbers before you schedule it. 4. **Schedule it** Ask your tool to run it on the schedule shown with the prompt. ## Calls it makes _To write: the sequence of Build calls this recipe makes, with one real request and response in CodeTabs_ ## Data used - [`get_campaign_performance`](https://build.sellermate.ai/docs/api-reference/get-campaign-performance.md) - [`get_search_term_performance`](https://build.sellermate.ai/docs/api-reference/get-search-term-performance.md) - [`get_orders_report`](https://build.sellermate.ai/docs/api-reference/get-orders-report.md) - [`get_inventory`](https://build.sellermate.ai/docs/api-reference/get-inventory.md) ## Variants Add one of these to the prompt: - Add a line for the launch date. - Show the top five search terms. - Make a page for each ASIN in a list. --- # Inventory Source: https://build.sellermate.ai/docs/recipes/inventory Work out days of stock per SKU, alert before you run out, and pause ads on Amazon when stock is low. - Amazon: Reads: yes · Writes: yes ## What you get Know when to reorder, and stop paying for ads on stock you do not have. The result is a Sheet and a Slack alert with the reorder date for every SKU, and on Amazon a nightly pause and resume of ads. _To write: the output mock for this recipe: a screenshot or sample of the real result, with numbers blurred_ ## The prompt Paste a prompt into your AI tool. Each one points the tool at the docs and at your key, which stays in `BUILD_API_KEY`. ### Days of stock and reorder For n8n. Schedule: Every morning at 7. Prompt for n8n: ``` Read https://build.sellermate.ai/SKILL.md. My key is in BUILD_API_KEY. Every morning, work out days of stock per SKU from my Amazon Seller stock and the last 30 days of orders, write the reorder date to a Google Sheet, and post a Slack message to #reorder for any SKU inside its 35 day lead time. ``` ### Stock-out ad protection For n8n. Schedule: Every night at 2. Prompt for n8n: ``` Read https://build.sellermate.ai/SKILL.md. My key is in BUILD_API_KEY. Build me an n8n flow that every night checks stock for each SKU with live Amazon Ads, pauses ads when fewer than 5 days of stock are left, resumes them after a restock, and logs every change to the Google Sheet stock-log. ``` > **Amazon only: The change step runs on Amazon accounts only** > > It needs a key with the read and write scope. It uses a dry run first, caps, a 24 hour undo and an audit log. See [Writes and guardrails](https://build.sellermate.ai/docs/guides/writes-and-guardrails.md). _To write: which tool applies the change in this recipe (negatives or an ad pause): the API reference lists update_target, and the negatives tool is not listed yet_ ## Steps 1. **Get a key** Create a key in the console and save it as `BUILD_API_KEY` in your tool's secrets. See [Get a key](https://build.sellermate.ai/docs/get-started/get-a-key.md). 2. **Paste the prompt** Pick the prompt above for your tool and paste it. Change the names in it, such as the channel or the Sheet, to yours. 3. **Run it once** Check the first result against your own numbers before you schedule it. 4. **Schedule it** Ask your tool to run it on the schedule shown with the prompt. ## Calls it makes _To write: the sequence of Build calls this recipe makes, with one real request and response in CodeTabs_ ## Data used - [`get_inventory`](https://build.sellermate.ai/docs/api-reference/get-inventory.md) - [`get_orders_report`](https://build.sellermate.ai/docs/api-reference/get-orders-report.md) ## Variants Add one of these to the prompt: - Use 45 days as the lead time. - Group SKUs that share a parent. - Alert only on the red ones. - Leave your top three SKUs alone. --- # Agency ops Source: https://build.sellermate.ai/docs/recipes/agency-ops Rank clients by what needs attention, watch budget pacing, check connections and audit a new account. - Amazon: Reads: yes · Writes: yes ## What you get Run many client accounts from one place. These four cover the daily look, the pacing check, the connection check and the pitch. The result is a ranked client board, one pacing line per client, an alert when a connection lapses, and an audit sheet for a new account. _To write: the output mock for this recipe: a screenshot or sample of the real result, with numbers blurred_ ## The prompt Paste a prompt into your AI tool. Each one points the tool at the docs and at your key, which stays in `BUILD_API_KEY`. ### What is on fire board For Claude Code. Schedule: Every morning at 7. Prompt for claude-code: ``` Read https://build.sellermate.ai/SKILL.md. My key is in BUILD_API_KEY. Every morning, read ACoS, spend and sales for every client and rank them worst first by ACoS drift, spend spike and sales drop in the Google Sheet client-board. ``` ### Budget pacing alert For n8n. Schedule: Weekdays at 9. Prompt for n8n: ``` Read https://build.sellermate.ai/SKILL.md. My key is in BUILD_API_KEY. Every weekday at 9, project month-end Amazon Ads spend for every client against their monthly budget and post one line each to Slack #pacing, flagging any client projected over 105%. ``` ### Connection health alert For n8n. Schedule: Every hour. Prompt for n8n: ``` Read https://build.sellermate.ai/SKILL.md. My key is in BUILD_API_KEY. Every hour, check each client’s Amazon connection in Build and post a Slack alert to #client-alerts when data is more than 24 hours old or access has lapsed. ``` ### 30-day account audit For Claude Code. Schedule: Whenever you have a pitch. Prompt for claude-code: ``` Read https://build.sellermate.ai/SKILL.md. My key is in BUILD_API_KEY. Audit the Amazon account I just connected: read the last 30 days of ads, inventory and costs, score waste, structure, inventory and margin out of 100, and write the biggest fixes to the Google Sheet audit. ``` ## Steps 1. **Get a key** Create a key in the console and save it as `BUILD_API_KEY` in your tool's secrets. See [Get a key](https://build.sellermate.ai/docs/get-started/get-a-key.md). 2. **Paste the prompt** Pick the prompt above for your tool and paste it. Change the names in it, such as the channel or the Sheet, to yours. 3. **Run it once** Check the first result against your own numbers before you schedule it. 4. **Schedule it** Ask your tool to run it on the schedule shown with the prompt. ## Calls it makes _To write: the sequence of Build calls this recipe makes, with one real request and response in CodeTabs_ ## Data used - [`get_campaign_performance`](https://build.sellermate.ai/docs/api-reference/get-campaign-performance.md) - [`get_inventory`](https://build.sellermate.ai/docs/api-reference/get-inventory.md) ## Variants Add one of these to the prompt: - Add Google Ads to the board. - Only flag a drift over 3 points. - Send the top three to Slack. - Use your agency name in the audit header. --- # Workspaces and accounts Source: https://build.sellermate.ai/docs/guides/workspaces-and-accounts How Build groups your marketplace and ad accounts, and how to connect several of them. > **Accounts are what you are billed on** > > A plan includes a number of accounts. A brand's Seller and Ads accounts on Amazon count as one account; Google Ads is a second. See [Plans and limits](https://build.sellermate.ai/docs/guides/plans-and-limits.md). ## The model _To write: a diagram and a short explanation of the model: user, workspace, accounts, keys. Say how a workspace relates to the SellerMate app if the CTO wants that stated publicly_ ## What counts as an account | You connect | Counts as | |---|---| | Amazon Seller, Vendor and Ads for one brand | One account | | Amazon DSP and AMC | To confirm | | Google Ads client account | One account | | Google Ads manager account (MCC) | To confirm | _To write: fill the two To confirm cells: whether DSP and AMC count within the brand's Amazon account, and whether each client under a manager counts as an account_ ## Agency or brand _To write: two short paths. Brand: connect your own accounts and use one key. Agency: connect each client, one key per client, and the hosted connect flow so a client approves in Build's page_ ## Connect several accounts _To write: steps for connecting a second and third account, how keys choose which accounts they reach, and what happens when you pass the plan's account count (an inline upgrade prompt, never a silent cut-off)_ ## Disconnect an account After you disconnect an account, its data is held for 30 days and then deleted. Billing stops at the next cycle. --- # Keys and scopes Source: https://build.sellermate.ai/docs/guides/keys-and-scopes How a Build key authenticates, what it can reach, and how to revoke or rotate it. ## Key types | Key | Looks like | Reaches | |---|---|---| | Live, read | `sm_live_…` | The accounts you chose, read only | | Live, read and write | `sm_live_…` | The same accounts. Can also change Amazon accounts, behind guardrails | | Sandbox | `sm_test_…` | Demo data, read only | ## Scopes Each key is scoped per key and per account. A key is either read, or read and write. A read key can never change anything. Writes exist on Amazon only; every other platform is read-only. _To write: the full scope list as the API names it, and which tools each scope allows_ ## Send the key Send the key in the `X-API-Key` header on every call. **curl** ```bash 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":"acct_123"}' ``` ## Revoke a key You can revoke a key in one click in the console, without touching the rest. Give each tool or client its own key so one revoke affects one thing. ## Rotate a key _To write: how to rotate: create the new key, switch the tool, revoke the old one. Say whether the console has a rotate action_ ## Keep a key safe - Store it as `BUILD_API_KEY` in your tool's secrets. Never put it in page code or in a prompt. - Use the sandbox key while you build. - Choose read unless the tool must change an Amazon account. --- # Plans and limits Source: https://build.sellermate.ai/docs/guides/plans-and-limits What each Build plan includes: accounts, data retention and requests per minute. ## Plans | | Free | Build | Scale | |---|---|---|---| | Price per month | $0 | $97 | $500 | | Accounts included | 1 | 3 | 10 | | Extra accounts | Upgrade | Upgrade | $33 each | | Data retention | 90 days | 12 months | 3 years | | Requests per minute | 60 | 60 | 300 | Build and Scale are 20% off when billed annually. ## On every plan - All core Amazon data: ads, orders, inventory, catalog and returns. - Google Ads data: campaign, ad group, keyword and search term performance. - Search Query Performance (SQP). - Writes on Amazon: create and change campaigns, ad groups, keywords, targets and bids, with guardrails. Every other platform is read-only. - REST API. - Every platform as it launches. ## Rate limits Requests per minute are counted per plan. Past the limit a call returns `429` with a retry time and a link to upgrade: ```json { "error": "rate_limited", "retry": 12, "upgrade": "https://build.sellermate.ai/pricing" } ``` _To write: what the limit is counted on (per key, per account or per workspace), burst behaviour, and whether the response carries rate limit headers_ ## Accounts past your plan Going past a plan's accounts prompts an inline upgrade. Nothing is cut off silently. _To write: overage: what happens on Build past 3 accounts, and how metered accounts on Scale are billed. Do not publish a figure that pricing.json does not hold_ ## Retention and downgrades Retention is how far back Build keeps your history. On a downgrade, data beyond the new retention is hidden for 30 days and restored if you upgrade. --- # Writes and guardrails Source: https://build.sellermate.ai/docs/guides/writes-and-guardrails How changes to an Amazon account work on Build: caps, a dry run, idempotency keys, a 24 hour undo and an audit log. > **Amazon only: Writes run on Amazon accounts only** > > Google Ads, Walmart, Flipkart, TikTok Shop and Meta Ads are read-only. A read key can never change anything. ## What you can change Bids, budgets, negatives and campaigns on Amazon Ads. Changes stay off until you turn them on, and a key needs the read and write scope. POST https://build-api.sellermate.ai/v1/tools/update_target — Change a target on an Amazon Ads account, behind caps, a dry run and undo. (writes: yes; platforms: Amazon) ## Caps Nothing moves past your limit. A request above a cap returns `422` and nothing is applied. _To write: where caps are set (console or API), which caps exist (bid, budget), and the default values_ ## Dry run A dry run shows what would change before anything is applied. _To write: how to ask for a dry run (parameter name), and a real dry-run response_ ## Idempotency keys _To write: the idempotency header or field, how long a key is remembered, and what a repeated request returns_ ## What a refused change looks like A bad bid gets a `422`, not a live campaign: ```json { "status": 422, "message": "bid 2.40 is above this account's ceiling of 2.00." } ``` Your code lowers the bid and tries again. The call that succeeds returns `200`, is logged, and can be undone for 24 hours. ## Undo for 24 hours _To write: how to undo a change: the endpoint or console action, and what cannot be undone_ ## Audit log Every write is logged: who, what, and the result. _To write: where to read the audit log (console and API) and the fields in an entry_ ## Approval mode _To write: what approval mode is, where it is turned on, and how a proposed change waits for a person to approve it_ --- # Webhooks Source: https://build.sellermate.ai/docs/guides/webhooks Webhooks are coming soon; until then, poll a tool and read data_as_of. > **Coming soon** > > Webhooks are not available yet. There is no date. This page will describe them when they ship. ## Planned events _To write: the events planned (for example a connection lapsing, a data set refreshing, a guarded change applied), the delivery format and signing_ ## Until then Call a tool on a schedule and read `data_as_of` on the answer to see how fresh it is. The [recipes](https://build.sellermate.ai/docs/recipes/agency-ops.md) show a connection health check you can run every hour. ## Join the waitlist _To write: where the webhooks waitlist form lives, if the CTO wants one_ --- # API reference overview Source: https://build.sellermate.ai/docs/api-reference/overview Every Build tool is one POST with a JSON body, the same fields on every platform, and an X-API-Key header. > **Illustrative call shape** > > The host and path below come from the current plan. They are illustrative until the contract is final. ## How a call works Each tool is one `POST` to `{tool name}` under the base URL, with one key in the `X-API-Key` header and a JSON body. **Shape** ```bash POST https://build-api.sellermate.ai/v1/tools/{name} X-API-Key: $BUILD_API_KEY Content-Type: application/json ``` Rows come back in the same fields on every platform. Every answer carries `data_as_of`. There is one live version, with `/v1` in the path, and breaking changes are announced in the [changelog](https://build.sellermate.ai/docs/changelog.md). ## Tools - [get_campaign_performance](https://build.sellermate.ai/docs/api-reference/get-campaign-performance.md): Reads. Amazon and Google Ads. Spend, clicks, orders, sales and ACoS for each campaign over a date range, in the same fields on Amazon and Google Ads. - [get_search_term_performance](https://build.sellermate.ai/docs/api-reference/get-search-term-performance.md): Reads. Amazon and Google Ads. Search terms with their clicks, spend and orders over a date range, on Amazon and Google Ads. - [get_orders_report](https://build.sellermate.ai/docs/api-reference/get-orders-report.md): Reads. Amazon. Orders and units for an Amazon Seller account over a date range. - [get_inventory](https://build.sellermate.ai/docs/api-reference/get-inventory.md): Reads. Amazon. Stock and inbound units for an Amazon account. - [update_target](https://build.sellermate.ai/docs/api-reference/update-target.md): Writes on Amazon only. Amazon. Change a target on an Amazon Ads account, behind caps, a dry run and undo. ## Common to every tool - Authentication: the `X-API-Key` header, a key scoped per account. See [Keys and scopes](https://build.sellermate.ai/docs/guides/keys-and-scopes.md). - Limits: requests per minute by plan. See [Plans and limits](https://build.sellermate.ai/docs/guides/plans-and-limits.md). - Writes: Amazon only. See [Writes and guardrails](https://build.sellermate.ai/docs/guides/writes-and-guardrails.md). _To write: the full tool list: this page lists the five tools in the API reference so far. Add the rest, and link the OpenAPI file and Postman collection once they exist_ --- # get_campaign_performance Source: https://build.sellermate.ai/docs/api-reference/get-campaign-performance Spend, clicks, orders, sales and ACoS for each campaign over a date range, in the same fields on Amazon and Google Ads. ## Endpoint POST https://build-api.sellermate.ai/v1/tools/get_campaign_performance — Spend, clicks, orders, sales and ACoS for each campaign over a date range, in the same fields on Amazon and Google Ads. (writes: no; platforms: Amazon, Google Ads) The call shape is illustrative until the contract is final. ## When to use it Use it for client reports, budget pacing, an exec card or a ranked board. Ask for the same dates on Amazon and Google Ads to put them side by side. ## Request fields | Name | Type | Required | Description | |---|---|---|---| | `account` | string | yes | The account to read. A key only reaches the accounts you chose when you created it. | | `start` | date | no | First day, as `YYYY-MM-DD`. | | `end` | date | no | Last day, as `YYYY-MM-DD`. | ## Response fields Every answer says how fresh it is with `data_as_of`. | Name | Type | Description | |---|---|---| | `platform` | string | The platform the row came from, for example `amazon` or `google_ads`. | | `account_id` | string | The account the row belongs to. | | `campaign_name` | string | The campaign, as named on the platform. | | `spend` | number | Spend over the period, in the account currency. | | `clicks` | number | Clicks over the period. | | `orders` | number | Orders over the period. | | `sales` | number | Sales over the period, in the account currency. | | `acos` | number | Spend divided by sales, as a fraction. | | `currency` | string | One currency per account. | _To write: confirm the exact types and units of each field, and add any field beyond these nine_ ## Examples **curl** ```bash 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":"acct_123","start":"2026-10-01","end":"2026-10-28"}' ``` **Node** ```js const res = await fetch("https://build-api.sellermate.ai/v1/tools/get_campaign_performance", { method: "POST", headers: { "X-API-Key": process.env.BUILD_API_KEY, "Content-Type": "application/json" }, body: JSON.stringify({ account: "acct_123", start: "2026-10-01", end: "2026-10-28" }), }); console.log(await res.json()); ``` **Python** ```python import os, requests res = requests.post( "https://build-api.sellermate.ai/v1/tools/get_campaign_performance", headers={"X-API-Key": os.environ["BUILD_API_KEY"]}, json={"account": "acct_123", "start": "2026-10-01", "end": "2026-10-28"}, ) print(res.json()) ``` **Response** ```json { "rows": [ { "platform": "amazon", "account_id": "amz_northwind", "campaign_name": "SP - Bottles - Exact", "spend": 1842.10, "clicks": 2210, "orders": 161, "sales": 6120.40, "acos": 0.301, "currency": "USD" } ], "meta": { "data_as_of": "2026-10-30T06:00:00Z" } } ``` _To write: replace with a real response from the API, including the real envelope around rows_ ## Errors ### 429 Too many requests You went over the plan's requests per minute. The body says when to retry. ```json { "error": "rate_limited", "retry": 12, "upgrade": "https://build.sellermate.ai/pricing" } ``` _To write: the other errors this tool can return, with the real status and body: a missing or wrong key, an account the key cannot reach, bad dates_ ## Platforms - Amazon: Reads: yes · Writes: yes - Google Ads: Reads: yes · Writes: no ## Open in your AI Paste this into Claude Code, Cursor, Lovable, n8n or Zapier. It points your AI at the docs and at your key. Prompt: ``` Read https://build.sellermate.ai/SKILL.md. My key is in BUILD_API_KEY. Use get_campaign_performance to show last week’s spend, sales and ACoS for each campaign, worst ACoS first. ``` --- # get_search_term_performance Source: https://build.sellermate.ai/docs/api-reference/get-search-term-performance Search terms with their clicks, spend and orders over a date range, on Amazon and Google Ads. ## Endpoint POST https://build-api.sellermate.ai/v1/tools/get_search_term_performance — Search terms with their clicks, spend and orders over a date range, on Amazon and Google Ads. (writes: no; platforms: Amazon, Google Ads) The call shape is illustrative until the contract is final. ## When to use it Use it to find search terms that spend and never sell, or to keep search-term history past the window the platform holds. Amazon keeps search terms for about 60 to 95 days; Build keeps them from the day you connect. ## Request fields | Name | Type | Required | Description | |---|---|---|---| | `account` | string | yes | The account to read. A key only reaches the accounts you chose when you created it. | | `start` | date | no | First day, as `YYYY-MM-DD`. | | `end` | date | no | Last day, as `YYYY-MM-DD`. | ## Response fields Every answer says how fresh it is with `data_as_of`. _To write: the response fields of a search-term row (the term, match type, clicks, spend, orders, sales and any hidden-by-Google marker)_ ## Examples **curl** ```bash curl -X POST https://build-api.sellermate.ai/v1/tools/get_search_term_performance \ -H "X-API-Key: $BUILD_API_KEY" \ -H "Content-Type: application/json" \ -d '{"account":"acct_123","start":"2026-10-01","end":"2026-10-28"}' ``` **Node** ```js const res = await fetch("https://build-api.sellermate.ai/v1/tools/get_search_term_performance", { method: "POST", headers: { "X-API-Key": process.env.BUILD_API_KEY, "Content-Type": "application/json" }, body: JSON.stringify({ account: "acct_123", start: "2026-10-01", end: "2026-10-28" }), }); console.log(await res.json()); ``` **Python** ```python import os, requests res = requests.post( "https://build-api.sellermate.ai/v1/tools/get_search_term_performance", headers={"X-API-Key": os.environ["BUILD_API_KEY"]}, json={"account": "acct_123", "start": "2026-10-01", "end": "2026-10-28"}, ) print(res.json()) ``` _To write: a real response with two or three rows_ ## Errors ### 429 Too many requests You went over the plan's requests per minute. The body says when to retry. ```json { "error": "rate_limited", "retry": 12, "upgrade": "https://build.sellermate.ai/pricing" } ``` _To write: the other errors this tool can return, with the real status and body: a missing or wrong key, an account the key cannot reach, bad dates_ ## Platforms - Amazon: Reads: yes · Writes: yes - Google Ads: Reads: yes · Writes: no ## Open in your AI Paste this into Claude Code, Cursor, Lovable, n8n or Zapier. It points your AI at the docs and at your key. Prompt: ``` Read https://build.sellermate.ai/SKILL.md. My key is in BUILD_API_KEY. Use get_search_term_performance to list search terms with 15 or more clicks and no orders in the last 30 days, costliest first. ``` --- # get_orders_report Source: https://build.sellermate.ai/docs/api-reference/get-orders-report Orders and units for an Amazon Seller account over a date range. ## Endpoint POST https://build-api.sellermate.ai/v1/tools/get_orders_report — Orders and units for an Amazon Seller account over a date range. (writes: no; platforms: Amazon) The call shape is illustrative until the contract is final. ## When to use it Use it for revenue and units in a weekly card, a month-end export, or days of stock. Sales keep moving for up to 14 days, and Build re-pulls those days until they settle (to confirm). ## Request fields | Name | Type | Required | Description | |---|---|---|---| | `account` | string | yes | The account to read. A key only reaches the accounts you chose when you created it. | | `start` | date | no | First day, as `YYYY-MM-DD`. | | `end` | date | no | Last day, as `YYYY-MM-DD`. | ## Response fields Every answer says how fresh it is with `data_as_of`. _To write: the response fields of an orders row, and where settling_from appears_ ## Examples **curl** ```bash curl -X POST https://build-api.sellermate.ai/v1/tools/get_orders_report \ -H "X-API-Key: $BUILD_API_KEY" \ -H "Content-Type: application/json" \ -d '{"account":"acct_123","start":"2026-10-01","end":"2026-10-28"}' ``` **Node** ```js const res = await fetch("https://build-api.sellermate.ai/v1/tools/get_orders_report", { method: "POST", headers: { "X-API-Key": process.env.BUILD_API_KEY, "Content-Type": "application/json" }, body: JSON.stringify({ account: "acct_123", start: "2026-10-01", end: "2026-10-28" }), }); console.log(await res.json()); ``` **Python** ```python import os, requests res = requests.post( "https://build-api.sellermate.ai/v1/tools/get_orders_report", headers={"X-API-Key": os.environ["BUILD_API_KEY"]}, json={"account": "acct_123", "start": "2026-10-01", "end": "2026-10-28"}, ) print(res.json()) ``` _To write: a real response with two or three rows_ ## Errors ### 429 Too many requests You went over the plan's requests per minute. The body says when to retry. ```json { "error": "rate_limited", "retry": 12, "upgrade": "https://build.sellermate.ai/pricing" } ``` _To write: the other errors this tool can return, with the real status and body: a missing or wrong key, an account the key cannot reach, bad dates_ ## Platforms - Amazon: Reads: yes · Writes: yes ## Open in your AI Paste this into Claude Code, Cursor, Lovable, n8n or Zapier. It points your AI at the docs and at your key. Prompt: ``` Read https://build.sellermate.ai/SKILL.md. My key is in BUILD_API_KEY. Use get_orders_report to total last week’s orders and units by day. ``` --- # get_inventory Source: https://build.sellermate.ai/docs/api-reference/get-inventory Stock and inbound units for an Amazon account. ## Endpoint POST https://build-api.sellermate.ai/v1/tools/get_inventory — Stock and inbound units for an Amazon account. (writes: no; platforms: Amazon) The call shape is illustrative until the contract is final. ## When to use it Use it to work out days of stock, alert before a stock-out, or decide when to pause ads on a SKU. ## Request fields | Name | Type | Required | Description | |---|---|---|---| | `account` | string | yes | The account to read. A key only reaches the accounts you chose when you created it. | ## Response fields Every answer says how fresh it is with `data_as_of`. _To write: the response fields of an inventory row (SKU, ASIN, fulfillable, inbound and any others)_ ## Examples **curl** ```bash 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":"acct_123"}' ``` **Node** ```js const res = await fetch("https://build-api.sellermate.ai/v1/tools/get_inventory", { method: "POST", headers: { "X-API-Key": process.env.BUILD_API_KEY, "Content-Type": "application/json" }, body: JSON.stringify({ account: "acct_123" }), }); console.log(await res.json()); ``` **Python** ```python import os, requests res = requests.post( "https://build-api.sellermate.ai/v1/tools/get_inventory", headers={"X-API-Key": os.environ["BUILD_API_KEY"]}, json={"account": "acct_123"}, ) print(res.json()) ``` _To write: a real response with two or three rows_ ## Errors ### 429 Too many requests You went over the plan's requests per minute. The body says when to retry. ```json { "error": "rate_limited", "retry": 12, "upgrade": "https://build.sellermate.ai/pricing" } ``` _To write: the other errors this tool can return, with the real status and body: a missing or wrong key, an account the key cannot reach, bad dates_ ## Platforms - Amazon: Reads: yes · Writes: yes ## Open in your AI Paste this into Claude Code, Cursor, Lovable, n8n or Zapier. It points your AI at the docs and at your key. Prompt: ``` Read https://build.sellermate.ai/SKILL.md. My key is in BUILD_API_KEY. Use get_inventory to list every SKU with fewer than 14 days of stock. ``` --- # update_target Source: https://build.sellermate.ai/docs/api-reference/update-target Change a target on an Amazon Ads account, behind caps, a dry run and undo. ## Endpoint POST https://build-api.sellermate.ai/v1/tools/update_target — Change a target on an Amazon Ads account, behind caps, a dry run and undo. (writes: yes; platforms: Amazon) The call shape is illustrative until the contract is final. > **Amazon only: Writes run on Amazon accounts only** > > Caps, a dry run, idempotency keys, a 24 hour undo and an audit log apply. See [Writes and guardrails](https://build.sellermate.ai/docs/guides/writes-and-guardrails.md). ## When to use it Use it to apply a bid change after your code or a person has approved it. Run a dry run first. It needs a key with the read and write scope. ## Request fields | Name | Type | Required | Description | |---|---|---|---| | `account` | string | yes | The account to read. A key only reaches the accounts you chose when you created it. | _To write: the other request fields: the target, the new bid or state, the dry-run flag and the idempotency key, with types, limits and examples_ ## Response fields Every answer says how fresh it is with `data_as_of`. _To write: the response of a dry run and of an applied change, including the log entry id and the undo handle_ ## Examples _To write: a dry-run request and response, then the applied request and response. Show the real field names for the target, the new bid and the dry-run flag_ ## Errors ### 422 Unprocessable A change above a cap is refused and nothing is applied. ```json { "status": 422, "message": "bid 2.40 is above this account's ceiling of 2.00." } ``` Lower the bid and send it again. ### 429 Too many requests You went over the plan's requests per minute. The body says when to retry. ```json { "error": "rate_limited", "retry": 12, "upgrade": "https://build.sellermate.ai/pricing" } ``` ## Platforms - Amazon: Reads: yes · Writes: yes ## Open in your AI Paste this into Claude Code, Cursor, Lovable, n8n or Zapier. It points your AI at the docs and at your key. Prompt: ``` Read https://build.sellermate.ai/SKILL.md. My key is in BUILD_API_KEY. Use update_target to run a dry run that lowers the bid on target tgt_123 to 2.00, and show me the result before applying it. ``` --- # Trust Source: https://build.sellermate.ai/docs/trust What Build claims today about keys, writes, credentials and data, and nothing more. This page states what is true today. ## Keys Each key is scoped per account and can be revoked at any time, in one click, without touching your other keys. A key is read, or read and write. See [Keys and scopes](https://build.sellermate.ai/docs/guides/keys-and-scopes.md). ## Read-only by default Build reads your data unless you allow changes. Writes exist on Amazon only. Every other platform is read-only. ## Writes are guarded Changes to an Amazon account run behind caps, a dry run first, a 24 hour undo and an audit log of every write. See [Writes and guardrails](https://build.sellermate.ai/docs/guides/writes-and-guardrails.md). ## Credentials Platform credentials are encrypted in the application. Build runs on AWS. ## Your data - Your data is never used to train anything. - After you disconnect an account, its data is held for 30 days, then deleted. ## What Build stores _To write: what Build stores per account (connection tokens, synced rows, the audit log) and for how long, by plan retention. Do not state a server location, SOC 2 or an SLA unless the CTO confirms it_ ## Data handling _To write: data handling details: who at Build can see data, how credentials are encrypted and where keys are held, how deletion works in practice, subprocessors_ ## Amazon terms _To write: what Amazon's developer terms require of Build and of customers, in plain words_ ## Terms and privacy Build is operated by SellerMate Technologies Private Limited. The [Terms](https://build.sellermate.ai/terms) and [Privacy policy](https://build.sellermate.ai/privacy) are SellerMate's. --- # Changelog Source: https://build.sellermate.ai/docs/changelog What changed in Build, newest first. Breaking changes are announced here. Build has one live version, with `/v1` in the path. Breaking changes are announced here. ## October 2026 ### 2026-10-30 · Google Ads is live (added) Platforms: Google Ads. Connect client and manager accounts from the console and read campaigns, ad groups, keywords, search terms and conversions under the same field names as Amazon. Google Ads is read-only. ## Dates to add _To write: Amazon live (Seller, Vendor, Ads, DSP and AMC under one key): the release date, then add it as a ChangelogEntry of type added for Amazon_ _To write: The developer console (sign in, connect an account, create keys): the release date, then add it as a ChangelogEntry of type added_ _To write: The Build Free plan (one account, a sandbox key, 90 days of data, 60 requests a minute): the release date, then add it as a ChangelogEntry of type added_