datawebotMercado Libre product data: listings, variations and catalog IDs
How Mercado Libre listings, seller offers, variations and catalog products fit together, and how to compare them by market and currency.
Updated · datawebot team
Get Mercado Libre data with datawebot
datawebot returns Mercado Libre search results and product pages as structured JSON: title, price, currency, availability and a link for each product. Run it from your AI agent over MCP or from your code over REST, at 5 credits per search page and 1 per product page. Failed pages are free, and every account starts with 200 free credits.
- Can I get Mercado Libre data with Python?
- Yes. Send the Mercado Libre URL to the REST API at api.datawebot.com with an API key from the dashboard, then read the JSON results. Any HTTP client works.
- What does Mercado Libre data cost?
- 5 credits per search page and 1 per product page. Failed pages are free. Every account starts with 200 free credits, and credit packs are one-time purchases with no subscription.
Connect your agent.
Search products across online shops and compare seller offers with direct links. Free email sign-in.
Agent setupWhy listings and catalog products are not interchangeable
Treat a Mercado Libre listing as a seller's marketplace offer. A linked catalog product can help with product matching, but it does not replace the listing, its seller, selected variation, price or local market. Keep each identity in its own field.
Scroll to compare →
| Record layer | What to preserve | What it identifies |
|---|---|---|
| Marketplace site | Country storefront and currency | The local marketplace and its currency; Mercado Libre runs separate local sites, such as Argentina, Brazil and Mexico. |
| Listing / offer | Listing identifier, seller and category | A concrete marketplace listing and the seller responsible for that offer. Do not deduplicate offers by title alone. |
| Selected variation | The selected option combination | The specific option combination, such as a size or color, when the listing has variations. |
| Catalog relation | Linked catalog product when present | A product-matching relationship. It does not identify the seller's price or replace the related listing and variation. |
| Price observation | Price, currency, source URL and observation time | A time-bound offer value. Keep it attached to the site, listing, seller and selected variation it describes. |
Choose a matching rule that preserves the offer
A product comparison often needs two grains: one row per seller offer and a separate product-level match. Use the catalog relation as a candidate link, then preserve the fields that let someone reproduce the comparison.
Scroll to compare →
| Comparison | Match or group by | Keep distinct |
|---|---|---|
| Same catalog product, different sellers | Use the linked catalog product as a product-level match when present; validate distinguishing attributes. | Keep each listing, seller, price, currency and observation time as a separate offer. |
| One listing with several options | Use the listing plus its selected option combination for an option-level observation. | Do not assume every variation has the same price, identifiers or catalog relation. |
| Same product on different country sites | Group only after a verified product match across local sites. | Retain the site, currency and each local listing and seller offer; a listing identifier is not a global product key. |
Content reviewed 2026-10-27.