# Elektra Mexico Scraper: Products, Prices & Marketplace Sellers (`latinamericadata/elektra-mexico`) Actor

Extract Elektra Mexico products, MXN prices, discounts, brands, SKUs and marketplace sellers. Monitor electronics, appliances and retail offers; export JSON, CSV or Excel.

- **URL**: https://apify.com/latinamericadata/elektra-mexico.md
- **Developed by:** [Latin America Data](https://apify.com/latinamericadata) (community)
- **Categories:** E-commerce
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 products

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Elektra Mexico Scraper & API

Extract **Elektra Mexico products, MXN prices and marketplace sellers** for recurring retail price monitoring. Compare phones, appliances, computers, furniture and other public catalog listings by brand, SKU and EAN. Export JSON, CSV or Excel through Apify.

Independent tool by Latin America Data. Not affiliated with or endorsed by Elektra.

### Quick start

```json
{"term":"refrigerador","maxItems":3,"maxRuntimeSecs":90}
```

For searches without a product or page cap:

```json
{"searchTerms":["refrigerador","lavadora"],"maxRuntimeSecs":600}
```

Automatic access recovery requires no customer proxy settings. There is no default product/page cap. Searches stop when the source ends, its pagination boundary is reached, or the time/spending budget expires. Earlier results are preserved.

### Commercial uses

- Monitor competitor prices, advertised discounts and assortment changes.
- Compare marketplace seller offers for the same SKU.
- Match products across retailers using EAN, brand and SKU where available.
- Build your own history through scheduled exports; historical prices are not supplied.

### Inputs

| Input | Meaning |
| --- | --- |
| term | Product, brand or category search. Default: refrigerador. |
| searchTerms | Optional 1-100 terms, replacing term; duplicates removed across terms. |
| maxItems | Optional overall product limit; none by default. |
| maxPages | Optional pages per term; none by default. |
| startPage | First page, default 1. |
| maxRuntimeSecs | Time budget, default 240 seconds, maximum 7200. |

Search relevance follows Elektra's public catalog search. Multiple words can broaden matching; this is not exact-phrase filtering. Accessories and related products may be included.

### Output and price interpretation

One row per unique parent `product_id` per run, with title, brand, selected SKU/EAN, MXN price, list price, discount percentage, availability, selected seller, categories, description, specifications, images, original URL, search term, page, rank and timestamp.

`offers` retains each SKU/seller price and availability. `variants` retains SKU names, EANs, images and source unit information. The headline price selects an available source-default seller first, then another available offer, then a priced unavailable offer, in source order. It is **not necessarily the lowest price**. No additional product fee is charged for nested offers or variants.

When all offers lack a published price and are unavailable, price is null and price_status is unavailable, never a fabricated zero-price offer. Such genuine catalog products are still delivered and charged. Source availability is for the public sales channel, not guaranteed stock or delivery to a postal code. No exact stock quantity is claimed. Financing installments are not the cash price and are not substituted for it. Shipping, conditional coupons and personalized prices are excluded.

### Pricing

**USD 0.004 per delivered unique product**, plus customer-paid Apify usage including compute, storage and automatic proxies when needed. 1,000 products cost USD 4.00 in product fees. Empty searches and diagnostics have no product fee; platform usage still applies. Set an Apify spending limit to control costs.

### Completeness and errors

Products are uploaded page by page. RUN_SUMMARY and DIAGNOSTICS are free records:

- success: genuine rows; inspect complete and stop_reason for limits.
- no_results: the source explicitly reports zero matching rows.
- partial: earlier rows preserved after an error or time/spending/source limit.
- blocked or failed: no valid rows obtained; the run fails visibly.

The actor uses Elektra's public VTEX JSON catalog, 50 products per page, sales channel 1. Range/count headers are verified. This endpoint limits starting offsets to 2,500. Larger searches stop explicitly with source_pagination_limit rather than pretending the whole catalog was retrieved; use more specific terms. Changing catalogs can also cause incomplete pages, which are reported rather than silently accepted.

The source can repeat products across pages. Duplicates are removed before billing and counted in the run summary, so the number delivered can be lower than the source's advertised total. An explicit successful empty JSON array is valid even when the source cache omits its count header. Completion means the returned search pages were exhausted, not guaranteed coverage of every product sold by Elektra.

See [VTEX's public search documentation](https://developers.vtex.com/docs/api-reference/search-api) for the underlying pagination contract. No login or private customer information is used. Source availability and unchanged responses cannot be guaranteed.

### API and scheduled exports

Use Apify's API or schedules for repeated price and seller comparisons. Keep the source URLs and timestamps for auditing. Respect applicable source terms and rules.

# Actor input Schema

## `term` (type: `string`):

Producto, marca o categoria.

## `searchTerms` (type: `array`):

Opcional. Sustituye term. Productos repetidos se guardan una sola vez.

## `maxItems` (type: `integer`):

Opcional. Sin limite predeterminado; continua hasta agotar resultados, tiempo o presupuesto.

## `maxPages` (type: `integer`):

Opcional. Sin limite de paginas predeterminado.

## `startPage` (type: `integer`):

Primera pagina consultada.

## `maxRuntimeSecs` (type: `integer`):

Presupuesto de tiempo para proteger el costo. Conserva los productos ya obtenidos.

## Actor input object example

```json
{
  "term": "refrigerador",
  "startPage": 1,
  "maxRuntimeSecs": 240
}
```

# Actor output Schema

## `products` (type: `string`):

No description

## `summary` (type: `string`):

No description

## `diagnostics` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("latinamericadata/elektra-mexico").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("latinamericadata/elektra-mexico").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call latinamericadata/elektra-mexico --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,latinamericadata/elektra-mexico"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/hgPWejY8PCzrJCs2n/builds/AxEt6galffOYxIok2/openapi.json