MercadoLibre Scraper

Scrape product listings from MercadoLibre — Latin America's #1 online marketplace — across every country site in one actor: Mexico (MLM), Argentina (MLA), Brazil (MLB / MercadoLivre), Chile (MLC), Colombia (MCO), Peru, Uruguay, and more. This MercadoLibre scraper returns rich, structured data per product — title, price, original price, currency, condition, seller, free shipping, category, attributes, location, permalink, and images — with no API key, no OAuth, and no login. Pay per result at $3.00 per 1,000 listings.

MercadoLibre product data this scraper returns

Each listing record contains the fields most teams need for pricing, sourcing, and market research:

Field	Description
item_id	MercadoLibre item ID (e.g. MLM1234567890)
title	Product title
price	Current selling price
original_price	Strikethrough / "before" price
currency_id	Currency (MXN, ARS, BRL, CLP, COP, …)
discount_pct	Discount percentage (computed)
available_quantity	Units available
sold_quantity	Units sold
condition	new or used
rating	Average star rating (0–5) when shown
reviews_count	Number of reviews when shown
installments	Financing string when shown (e.g. "12x sin interés")
seller_id / seller_nickname	Seller identity
seller_reputation	Seller reputation level when shown
free_shipping	Whether the listing offers free shipping
listing_type	Listing tier when present
category_id	MercadoLibre category ID
attributes	Brand, model, and other item attributes
location_state / location_city	Item location
permalink	Canonical product URL
thumbnail / pictures	Image URLs
site / country	Source site (MLM/MLA/…) and country code
parse_confidence / warnings	Data-quality score + drift flags
scraped_at	ISO-8601 scrape timestamp

How to scrape MercadoLibre in any country

Pick a country site and a search query, and the actor does the rest. It paginates the storefront automatically and pushes one clean record per product.

• site — MLM (Mexico, default), MLA (Argentina), MLB (Brazil), MLC (Chile), MCO (Colombia), and 13 more.
• sites — scrape several countries in one run. A list of site IDs; every query runs against each one (e.g. compare a price across Mexico, Argentina and Brazil at once). Leave empty to use the single site.
• query — a single search term, like the MercadoLibre search bar.
• queries — a list of searches run in sequence (batch competitive research).
• itemUrls — specific product URLs or IDs for price monitoring.
• sellerUrls — seller / official-store pages.

{
  "site": "MLM",
  "query": "iphone 15",
  "maxResults": 50
}

Compare one query across three countries in a single run:

{
  "sites": ["MLM", "MLA", "MLB"],
  "query": "iphone 15",
  "maxResults": 50
}

MercadoLibre data: use cases

• Price monitoring — track price, discount, and stock changes for competitor SKUs across countries.
• Market research — survey a category's pricing landscape, brand mix, and seller fragmentation.
• Arbitrage sourcing — find discounted, high-demand items to resell across LATAM marketplaces.
• Seller intelligence — profile sellers by reputation, range, and free-shipping policy.
• Repricing & feeds — feed normalized MercadoLibre prices into a repricer or BI dashboard.

Multi-country coverage (MLA, MLB, MLM, MLC, MCO and more)

One actor, all 18 of MercadoLibre's marketplaces. The site input selects a single storefront; the sites input scrapes several countries in one run, routing each through a residential IP in its own country so every result reflects what a local shopper actually sees. Brazil (MercadoLivre, lista.mercadolivre.com.br, Portuguese) is fully supported alongside the Spanish-language sites — including its special domain and subdomain, which single-language scrapers get wrong. Run one query across MX + AR + BR and get a clean, side-by-side price comparison without launching three separate jobs.

Why this MercadoLibre scraper is reliable

MercadoLibre's public API is now OAuth-gated and rejects anonymous requests, and its storefront blocks datacenter IPs on search. This actor handles both realities: it reads the storefront's embedded polycard JSON with a structural-HTML fallback, and it routes through Apify Residential Proxy in the target country (no external proxy account, no key to paste — proxy cost is already included in the per-result price). A built-in parse_confidence score and warnings list flag silent structure drift, so you catch breakage before it pollutes your dataset.

A three-layer parser that keeps working when the page changes

Marketplaces reshuffle their markup constantly, and most scrapers break the day they do. This one is built as a guarded fallback chain, each layer emitting a parse_confidence score:

1. Polycard JSON (primary) — the structured product objects embedded in the page. Fast and complete.
2. Deep state walk (B-plan) — if MercadoLibre renames the results wrapper key, the parser walks the embedded state tree and finds the largest array of product-shaped objects anywhere in it. A key rename no longer blinds the scraper.
3. Structural HTML (last resort) — when no JSON is present at all, it parses the result grid using stable structural anchors (ui-search-layout__item, poly-card, andes-money-amount), not brittle hashed CSS classes.

On top of that, the actor detects access interstitials (the "account verification" / verification pages) and rotates to a fresh residential IP before retrying, and it never charges you for empty or low-confidence records — a broken parse produces no garbage in your dataset and no charge on your bill. If a whole run is blocked, it fails loudly instead of handing you a silent empty dataset.

Pricing

Pay Per Result: $3.00 per 1,000 listings ($0.003 per record). You only pay for clean records the actor actually pushes. Platform/proxy usage is billed to your own Apify account at standard rates.

Frequently asked questions

Do I need a MercadoLibre account or API key? No. The actor reads the public storefront — no login, no OAuth, no token.

Which countries are supported? All MercadoLibre sites: Mexico, Argentina, Brazil, Chile, Colombia, Peru, Uruguay, Venezuela, Ecuador, Bolivia, and the Central-American sites — selected via the site input.

Do I need a proxy? Yes for search — MercadoLibre blocks datacenter IPs. The actor defaults to Apify Residential Proxy in the site's country; just leave the proxy input on its default. It is billed to your Apify account.

Can I look up specific products? Yes — pass product URLs or item IDs (e.g. MLM1234567890) in itemUrls.

What does parse_confidence mean? 1.0 means all critical fields parsed cleanly. Records below 0.5, or missing both an ID and a price, are dropped before the dataset — you are never charged for them. Check warnings for the specific drift codes.

Why is there no monthly fee? This actor is pure pay-per-result — you pay only for listings actually delivered. There is no rental or subscription on top.

Integrations

Built for e-commerce sellers and market researchers tracking pricing, competitors, and demand across Latin America — the JSON/dataset output drops into the tools you already run, no glue code:

• n8n / Make / Zapier — trigger a run or pipe every new dataset item into 500+ apps (Google Sheets, Airtable, Slack, HubSpot, your database) with no code: n8n, Make, Zapier.
• Webhooks — fire your own endpoint the moment a run finishes, to push results straight into your pipeline (docs).
• MCP server — expose this actor as a tool to Claude, Cursor, or any MCP client so an AI agent can pull this data mid-conversation (guide).
• API & SDKs — fetch the dataset as JSON, CSV, or Excel through the Apify REST API or the Python / JS SDKs.

See all Apify integrations.

Disclaimer

MercadoLibre is a public marketplace. This actor accesses the same publicly visible storefront pages any shopper can browse, and extracts only publicly available listing data.

More scrapers from our toolkit

Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:

• Olx Listings
• Poshmark Listings
• Shopify Products Scraper
• Tiktok Shop Scraper
• Uber Eats Menu Scraper
• Vinted Marketplace

Chain any of them together from the Integrations tab (the Run succeeded trigger) to build a multi-step workflow — one actor's output feeds the next.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.