Americanas and Magazine Luiza data from one API
Brazilian price comparison runs through both of these, and the same SKU frequently carries different prices and different sellers on each. One key covers both, with the seller and shipping surfaces that decide which offer is actually cheaper.
Both run seller-facing APIs: they return YOUR catalogue once you are an approved merchant, not the marketplace's. For reading public prices across either, they do not apply.
Coverage
What the two engines give you
- Americanas
- search, category, product/detail, product/batch, seller/products, filters
- Magazine Luiza
- search, category, product/detail, product/reviews, product/shipping
- Batch
- Americanas takes a batch of products in one call
- Shipping
- Magalu exposes shipping as its own endpoint
Worked example
Price one product across both
Search each side, then read the detail; the delivered price needs Magalu's shipping call.
- 1
POST /americanas/v1/searchfind the product, take its id
- 2
POST /americanas/v1/product/detailprice and the seller behind the offer
- 3
POST /magalu/v1/searchthe same product on Magalu
- 4
POST /magalu/v1/product/shippingdelivered cost, which often flips the ranking
Two sticker prices and one delivered price, for the same product, in four calls.
Before you join them
Where the two sources genuinely differ
| americanas | magalu | |
|---|---|---|
| Reviews | not exposed as its own endpoint | product/reviews |
| Shipping | not exposed separately | product/shipping |
| Bulk | product/batch for many ids at once | no batch endpoint |
| Sellers | seller/products lists a seller's catalogue | no seller endpoint |