Cyberpuerta Mexico Scraper: Product Prices, Stock & API

Extract Cyberpuerta Mexico product search results with MXN prices, brands, availability and product links. Designed for retail price monitoring, catalog research and repeated competitor comparisons. Export the dataset as JSON, CSV or Excel, or run through the Apify API.

This is an independent tool by Latin America Data, not an official Cyberpuerta API and not affiliated with or endorsed by Cyberpuerta.

Quick start

{"term":"monitor","maxItems":3,"maxRuntimeSecs":90}

Run several searches:

{"searchTerms":["monitor samsung","monitor lg"],"maxRuntimeSecs":240}

Input

Field	Behavior
term	Search phrase, brand or model.
searchTerms	Optional list replacing term. Duplicate products across terms are removed.
maxItems	Optional maximum unique products for the whole run. No default result cap.
maxPages	Optional maximum pages per term. No default page cap.
startPage	One-based starting page, default 1.
maxRuntimeSecs	Safety budget, default 240 seconds, maximum 7200. Earlier results are retained.
requestTimeoutSecs	Request timeout, default 30 seconds.

No proxy configuration or account credentials are required from the user. Connection routes are handled automatically. The short example is intentionally cheap; remove maxItems to continue until the source ends, the runtime budget expires or the Apify spending limit is reached.

Output

Successful product rows contain status, country, source, product_id, sku, ean, title, brand, price, list_price, currency, available, reported_quantity, image_url, source_url, search_term, page, rank and scraped_at. Additional fields include source-specific specifications, ratings and shipping information. Fields not supplied by the source remain null; no values are invented.

Products are saved progressively after each page, with deterministic page order and duplicate removal. RUN_SUMMARY records search progress, completion, stop reason, requests, retries, response bytes and time to the first delivered result. Proxy byte figures measure response bodies, not Apify's billable traffic.

Status and errors

• success: real validated products.
• no_results: source confirms an empty search, with no product charge.
• blocked: source denies access or returns a verification page.
• failed: invalid input, unavailable source or changed data format.
• partial: earlier products were saved, but a later page or budget prevented completion.

Operational diagnostic rows are not charged as products. A blocked page is never treated as a valid empty search. A run with no usable products and an access/error condition fails visibly; inspect RUN_SUMMARY for detail.

Pricing

USD 0.003 per unique validated product delivered (USD 3 per 1,000 products), plus Apify platform consumption paid by the user, including compute, storage and proxies where used. Configure an Apify spending limit for a hard cost boundary. Empty results and diagnostic rows do not incur the per-product event.

Source and limitations

Country: Mexico. Source contract: Cyberpuerta's Nuxt server-rendered catalog data, including prices, stock, identifiers and specifications. Pagination follows the storefront's next-page links.

The source can rate-limit or block requests. Automatic Mexican proxy fallback is built in, but successful access cannot be guaranteed. Listed stock and shipping prices are source-reported and can change with destination or checkout. Some returned page sizes vary; the actor does not stop merely because a page has fewer products.

Use the data lawfully and respect source terms and applicable restrictions. Search-result coverage does not imply access to private accounts, checkout-only prices or the entire retailer inventory.

API and automation

Use the Actor's API tab for the current run endpoint and generated Python/JavaScript examples. Schedule repeated runs and compare product_id or sku over time to monitor changes. Dataset output fields remain consistent between scheduled and manual runs.