Amazon Latin America Catalogue by Category

Pulls every product Amazon shows on a browse-node listing in Latin America, page by page, on amazon.com.br and amazon.com.mx. One row is one product card in the order shoppers see it. Use it to rebuild a category's assortment in Brazil and Mexico, track prices in BRL and MXN, and measure how much of a shelf is sponsored.

What you get

• Every card on the listing with page and position, so shelf order is preserved.
• is_sponsored on every row, taken from the card's own Patrocinado label, so paid slots stay separable from organic ones.
• Pricing: price, the struck-through original_price and currency (BRL or MXN).
• Demand signals: rating, rating_count, badges and the delivery promise printed on the card.
• Identity per product: asin, name, brand, image_url and product_url.
• Category context on every row: category, category_title, parent_category and breadcrumbs.
• Optional subcategory crawl: set expandSubcategories and each node's children are crawled too.

Input

Give it one or more browse-node ids or listing URLs and pick the storefront.

{
  "categories": ["16754344011"],
  "locale": "br",
  "maxPages": 1,
  "expandSubcategories": false,
  "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"], "apifyProxyCountry": "BR" },
  "delayMs": 1500
}

• categories (required): node ids such as "16754344011", a /b?node= link or an /s?rh=n%3A... listing URL. Ids sit under Mais Vendidos and in the left Departamento nav.
• locale: br for amazon.com.br, mx for amazon.com.mx. Default br.
• maxPages: pages per node, 0 means every page.
• proxyConfiguration: residential proxy in the storefront's country, already defaulted to residential BR.

Output

One row per product card on one listing page.

{
  "platform": "amazon-latam",
  "locale": "br",
  "category": "16754344011",
  "breadcrumbs": "Departamento",
  "page": 1,
  "position": 1,
  "asin": "B08GHGJ8WH",
  "name": "Lisa Esfoliante Pitaya e Roma - Bio Soft",
  "brand": null,
  "price": 10.9,
  "original_price": 12.82,
  "currency": "BRL",
  "rating": 4.7,
  "rating_count": 1700000,
  "in_stock": true,
  "is_sponsored": true,
  "badges": [],
  "delivery": "Entrega GRATIS: qua., 16 de set. no seu primeiro pedido",
  "product_url": "https://www.amazon.com.br/dp/B08GHGJ8WH",
  "fetched_at": "2026-09-12T02:57:35.107Z"
}

seller is always null on listing rows, Amazon does not print it on a category card. brand is null for most products: today's Amazon cards carry no brand line, and the brand is part of name. It is filled for books and media, where the card prints a byline. For a reliable brand per product, pass the ASINs to the matching Amazon product details actor. original_price is null when nothing is struck through.

Use cases

• Price and list-price tracking across a category in Brazil and Mexico, using price and original_price.
• Share of shelf: match your products by asin or name and count them against the category total per page and position.
• Ad-slot share: is_sponsored shows which competitors buy the top of each page.
• Assortment and stock gaps: in_stock plus delivery shows what is listed and what ships late.

Notes and limits

• A listing page carries roughly 48 to 60 cards. Browse-node listings go up to about 400 pages per node.
• Keyword search is capped by Amazon at 7 pages. This actor reads browse nodes, so it is not affected.
• A residential proxy inside the storefront's country is needed, BR for Brazil and MX for Mexico.
• Both storefronts use a comma as the decimal separator. Prices are parsed with that convention, so price is always a plain number.
• A category id that cannot be resolved is skipped and counted in failed_categories instead of failing the run.
• Live amazon.com.br runs: one node over one page returned 58 products with 10 sponsored, the same node over 3 pages returned 153.

FAQ

Do I need a proxy? Yes, residential in the storefront's country: BR for amazon.com.br, MX for amazon.com.mx. The actor already defaults to residential BR.

How many results can I get? About 48 to 60 products a page and up to roughly 400 pages per node, so a large node runs into tens of thousands of rows. Cap it with maxPages.

Does it need a login or an API key? No. Public listing pages only, no Amazon account and no seller credentials.

How are sponsored placements detected? From the Sponsored label Amazon prints on the card, so is_sponsored matches what a shopper in Brazil or Mexico sees.