Amazon Creators API

Use Case Scenarios

• A watchlist that refreshes itself

  A list of ASINs lives in Google Sheets, one row per product the team writes about. On a schedule the agent reads the rows, batches them ten at a time into Get Items, and calls Get Item Offer for the flattened price, currency, availability and affiliate link. Rows are matched back on the asin field rather than on request order, because the response does not preserve it and invalid ASINs move to a separate errors list. Movers append back to the sheet with a timestamp, and a summary posts to Slack naming only the products whose price or stock state actually changed.

• Catalog enrichment without the copy and paste

  An internal product catalog in Airtable carries names and internal codes but no imagery and no competitive price. The agent runs Search Items against the marketplace for each record, uses Get Variations to pull the full family when the match is a single variant, and writes the title, image URL and price back onto the record. Get Browse Nodes resolves the category tree so a search can be narrowed to the niche the product actually sits in rather than the whole marketplace, which is usually the difference between a useful match and a plausible wrong one.

• The sweep that reports its own blind spot

  A merchandising analyst wants the newest arrivals in a category. The agent calls Search Items All Pages, which walks consecutive pages and pauses between them so the account's transaction rate is respected, and stops at the first empty page. It then reports two numbers side by side: the total the marketplace claims for that query, and the number of items the ceiling actually allowed it to retrieve. The analyst reads both before deciding whether the shortlist is a fair sample or a coincidence of ranking, and the workflow never writes a recommendation the evidence cannot carry.