Amazon Scraping, History & Search API
The Logimu API scrapes Amazon product pages and search results on demand. Attach full product history to any response — price, seller, buy-box and BSR. Or skip the scrape and answer from our Amazon warehouse in under 100 ms. Self-serve, never billed for a failed request, plans from $19/month with a 14-day money-back. Free live demo, no account.
- ✓Schedule batch runs using GUI or API
- ✓Warehouse product data with history
- ✓Live scrape for current Amazon data
- ✓Continuously refreshed warehouse of 24M+ products
- ✓Bulk: up to 20,000 ASINs per batch, priced before you run
- ✓11 Amazon marketplaces + US Walmart
- ✓Self-serve API — no proxies, captchas or parsers to maintain
Search your own products. See what the API returns.
The demo doubles as a coverage check: enter one of your ASINs, a barcode, a keyword or an Amazon product link. A product we hold shows its full record and history; one we don’t hold yet is fetched live from Amazon.
The operator network behind a brand, live.
This is the real Nike seller network — every brand below shares Amazon buy-box sellers with Nike, drawn from our observed daily record. The Logimu API serves exactly this object: GET /v1/brand/network?brand=Nike&country=us returns the nodes[] and weighted edges[] you see drawn here, one credit per hop. Hover a brand for its numbers; click one to recenter; type any brand to map it.
Node colour is the brand’s heat (seller pressure: how many sellers per listing and how fast that is rising), size is its catalogue, distance is how many sellers two brands share. Counts and shares from observed buy-box data, refreshed daily — never estimates. Available on every paid plan. Endpoint reference →
What you get.
-
Two ways to answer the same call
mode=cachereturns from a continuously refreshed warehouse of 24M+ products in under 100 ms.mode=liveruns an on-demand scrape against Amazon for that one request. Same endpoint, same schema, your choice per call. -
History the live-only APIs cannot return
Price and stock change events come back in the base product call. Add
bsr_history=truefor daily rank per category back to Oct 2023 on Amazon US, oroffer_history=truefor a buy-box timeline and per-seller price series. - One schema across 12 marketplaces Title, price, seller name and ID, FBA/FBM flag, BSR rank and category, review count, rating, ASIN, UPC, brand, availability and variation data — identical field names across 11 Amazon marketplaces and Walmart US. Nothing to re-map per country.
- Failures are never billed A miss, an empty result or an incomplete scrape costs nothing. Bulk work runs through CSV batches of up to 20,000 ASINs, priced before you run it.
What a product response includes.
One ASIN in, the full record out — /v1/product.
-
Warehouse or live scrape — your call
mode=cacheanswers in under 100ms for half a credit.mode=livescrapes the listing on demand when it has to be current. Failed scrapes are never billed. - Current snapshot Title, brand, price and currency, the main image, BSR — plus the best category rank for the products that carry no overall rank — rating, review count, stock state, UPC, parent ASIN, the canonical product URL, and brand stats. Amazon's own "bought in past month" figure comes too, where it publishes one.
-
Every seller, in the same call
The full live offer list is standard, not a separate endpoint: every seller with name and ID, price and shipping cost, condition, FBA and Prime flags, positive-feedback percentage, lifetime feedback count, and buy-box days. New and used offers are split out, each with its own lowest offer and count. The buy box and the first offer page come by default;
full_offers=truewalks every further page inside the same call for the same single credit. Gathering offers is the slow part of any live scrape, which is why most APIs bill them separately — a paginated offers endpoint at a credit per page of 10 makes a 30-seller listing four requests there and one here. - Price and stock history The full price series plus price-change and stock-change events, in the base call.
-
Rank history, per category
Add
bsr_history=truefor daily rank in every category the product sits in. Included in the record. -
Seller history — who held the buy box, and when
Add
offer_history=truefor a buy-box timeline plus a per-seller price series, each with first seen, last seen and buy-box days. Included in the record, like the rank history. - Fulfilment — AMZ, FBA or FBM Who actually ships it: the buy-box winner's fulfilment type, per-offer FBA and FBM flags, a count of each across the listing, and whether Amazon itself is selling or holding the box.
- Delivery days Read from Amazon's own delivery sentence at the time of the observation — earliest and latest days, the fastest Prime option where one is shown, and the promised date, for the buy box and for every offer.
- The page content itself Description, feature bullets, the full image gallery, category breadcrumbs, and variations with parent ASIN — plus featured customer reviews carrying author, star rating, title, body, verified-purchase flag, review date and helpful count. Each block is stamped with when the content was last captured.
Both endpoints cover eleven Amazon marketplaces plus US Walmart, in one schema.
What a search response includes.
Keyword or barcode in, ranked products out — /v1/shopping.
- Ranked, grouped shortlists Broad queries group by category; specific ones come back as Budget / Mid-range / Premium tiers.
-
Full product records
ASIN, title, brand, price, rating, review count, stock, FBA flag, image, category path and an
observed_atstamp. - Brand and category facets Product count, average rating, total ratings and estimated monthly units sold, per brand.
-
Keyword or barcode
Pass a UPC, EAN, GTIN or ISBN-13 as the query: it resolves to its product from the listings we observe or the same product on another Amazon marketplace (for any barcode at all,
/v1/product?gtin=also asks Amazon’s own search). Unknown barcodes are never billed.
Side-by-side comparison.
Competitor figures below are from their own published documentation and from independent 2026 benchmarks, not from their marketing pages.
| Logimu | ScraperAPI | Oxylabs | Bright Data | |
|---|---|---|---|---|
| Architecture | Maintained warehouse + live scrape on demand | Live scrape per request | Live scrape per request | Live scrape per request; datasets sold separately |
| Price, BSR & buy-box history in the API | Included in the same call | — | — | — (separate dataset purchase) |
| Full multi-seller offer list | In the same product call | Separate /structured/amazon/offers endpoint |
Separate amazon_pricing source |
Separate Sellers scraper |
| Ranked, grouped search lane | Yes — /v1/shopping, under 100 ms |
Live SERP scrape | Live SERP scrape | Live SERP scrape |
| Cost known before a bulk run | Yes — free /v1/batch-estimate returns the credit cost first |
No — run the job to price it | No — run the job to price it | No — run the job to price it |
| Pricing model | Published credits, 1–2 per call, no endpoint multipliers | Credits, about 5 per Amazon structured request | Per successful result | Per delivered record |
Gathering every offer on a listing is the slow, awkward part of an Amazon scrape, which is why all three sell it as a second billed call — a separate endpoint at ScraperAPI, a separate amazon_pricing source at Oxylabs, a separate Sellers scraper at Bright Data, and paginated at Rainforest with credits charged per page. Here the full current offer list — seller name and ID, price, FBA and Prime flags, feedback score and buy-box days — comes back inside the product call (first page by default, every page with full_offers=true, one credit either way — a 30-seller listing is one call here and, at 10 offers per page, four requests on a paginated offers endpoint). What none of them will do is answer in under 100 ms, hand you price, rank and buy-box history in the same call, return every seller on the listing without a second billed request, or tell you what a 20,000-ASIN job costs before you run it.
Common use cases.
- Price monitoring Track competitor pricing across thousands of ASINs with daily or intra-day snapshots. Detect MAP violations, unauthorized sellers, and pricing anomalies.
- Competitive intelligence Monitor BSR movements, new seller entries, review velocity, and Buy Box ownership changes across your category.
- Brand protection Identify unauthorized third-party sellers, counterfeit listings, and hijacked product pages with structured offer-level data.
- Market research Build category-level datasets covering pricing distribution, seller landscape, review sentiment, and product availability trends.
Switching is one endpoint and one schema.
There is no pipeline to design and no per-country mapping to write. The whole surface is three endpoints: /v1/shopping for a ranked shortlist from a keyword or barcode, /v1/search to filter the warehouse, and /v1/product for everything about one ASIN — current snapshot, every seller on the listing, and history — in a single call.
Point an existing integration at it by changing the host and the field names once. Proxy rotation, headless browsers, captcha handling and the parser fixes that follow every Amazon layout change all sit behind the endpoint instead of in your codebase. When you need what Amazon is serving right now rather than what we last observed, it is the same call with mode=live.
Requests that miss, return empty or scrape incompletely are never billed, so finding the edge cases in your own catalogue costs nothing. Plans start at $19/month with a 14-day money-back, and bulk work runs as a CSV batch of up to 20,000 ASINs, priced before it runs.
vs. the Product Advertising API.
Amazon retired PA-API v5 in May 2026. Its replacement ties access to an Associates account and raised the qualifying-sales bar, and like PA-API before it, it was never built to answer the questions this API answers: BSR rankings, the full offer list and seller identities are not part of it.
Logimu needs no Associates account and no affiliate traffic. One call returns the current snapshot, every seller on the listing, and price, rank and buy-box history, across 11 Amazon marketplaces and Walmart US.
Derived intelligence: what the observations add up to.
Every product we observe is also an observation about a brand, a seller and a category. The same key serves those aggregates — computed daily from observed buy-box data, never estimated, with data_source on every answer.
- Brand dossier —
GET /v1/brand: how many sellers win the buy box on a brand, Amazon’s own share, FBA penetration, seller concentration and churn, trend grades, benchmarks against its category, the top sellers; monthly history on request. - Seller map —
GET /v1/brand/network: the brands connected to a brand because the same third-party sellers win the buy box on both — weighted edges and node metrics, one hop per call. See it drawn live on the homepage → - Operator footprint & category landscape —
GET /v1/seller/brands,/v1/seller/network,/v1/category: every brand a seller was observed winning on, the sellers that win beside it, and a category’s size, Amazon share, FBA share and concentration — plus ranked lists of brands, sellers and categories.
1 credit per record, 1 per page of 25 rows, lookups and misses free; part of every paid plan. Endpoint reference →
Amazon stats inside Claude & ChatGPT.
Prefer tool calls in your assistant over raw API calls? Webotee AI Connect puts this same Amazon data to work inside Claude & ChatGPT — product search and shopping lookups like this API’s, plus a wide set of Amazon market stats and research tools: brand intelligence, seller networks, niche & category discovery, and AI-assisted evaluations grounded in observed data. Built by the team behind Logimu; plans from $19/month.
Run it against your own ASINs.
The demo above hits production. Put your own ASINs or search terms through it, then get an API key from $19/month and make the same call from your code. Cancel anytime, 14-day money back.
Sign up