# Joom Scraper - Products, Prices, Discounts & Reviews (`abotapi/joom-com-scraper`) Actor

Scrape Joom products by keyword or URL. Extract product names, prices, discounts, sellers, ratings and images, with optional detailed descriptions, variants and customer reviews. Supports product, search and category URLs for flexible data collection.

- **URL**: https://apify.com/abotapi/joom-com-scraper.md
- **Developed by:** [Abot API](https://apify.com/abotapi) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.20 / 1,000 product records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## Joom Scraper: Products, Prices and Discounts

Joom Scraper turns Joom, a global mobile-first discount marketplace with millions of products from thousands of sellers, into a clean product feed. Search by keyword, or paste any product, search, category or collection link and the actor reads the marketplace's own listing pages directly: current price and discount with the original price derived, store, category and rating, on every row without a second request. Turn on one toggle for the description, variant summary, image gallery, store rating, rating histogram and review texts. Export to JSON, CSV or Excel, or pull results straight into your app through the API.

### Why This Scraper?

- **Four ways in.** Search by keyword, or paste a product, search, category or collection link; a pasted link decides its own scope.
- **The full price story on every row.** Selling price, discount percentage and the derived original price arrive from the listing itself, with no second request and no toggle required.
- **Store and rating on every row.** Store name, category, rating and review count come straight off the listing card.
- **Details on demand.** Turn on Fetch product details for the description, variant summary with sizes and colours, image gallery, store rating, rating histogram and review texts.
- **Built for monitoring.** Incremental mode returns only new, changed and reappeared products on recurring runs, and a refused run fails loudly instead of returning an empty dataset.

### Use Cases

- **Who:** discount hunters tracking flash deals across categories.
- **Who:** pricing analysts watching how seller prices and discounts move over time.
- **Who:** assortment researchers getting notified when a product appears, disappears, or changes stock state.
- **Who:** store analysts comparing seller ratings and review volumes.

### Data You Get

> Sample shape: values are illustrative placeholders, not from a live record.

| Field | Example |
| --- | --- |
| `recordId` / `rowType` | `"joom:682abb4b90498f0131f1881a"` / `"product"` (the marketplace's own stable product id) |
| `title` | `"Sample Wireless Headphones with Charging Case"` |
| `price` / `currency` | `8.78` / `"USD"` (the current selling price and the currency the row was priced in; the marketplace prices by serving region, so the currency follows the connection's exit and can differ between runs) |
| `originalPrice` / `onSale` / `discountPercent` | `10.97` / `true` / `20.0` (the original price is derived from the served price and discount) |
| `category` / `categoryId` | `"T-shirts"` / the category id |
| `storeId` / `storeName` / `storeRating` | the store id, `"Sample Store"` and `4.6` (name and rating with Fetch product details on) |
| `averageRating` / `reviewCount` / `reviewCountText` / `ratingDistribution` | `4.7` / `2000` / `" / 2,000+"` / per-star counts (histogram with Fetch product details on) |
| `inStock` | `true` (the orderable flag) |
| `imageUrl` / `imageUrls` / `url` | product image, the full gallery and the product page link (gallery with Fetch product details on) |
| `description` | with Fetch product details on: the product text |
| `minPrice` / `maxPrice` | with Fetch product details on: the variant price span |
| `shippingMinPrice` / `shippingMaxPrice` / `shippingCurrency` | with Fetch product details on: the shipping price span |
| `variantsCount` / `variantSizes` / `variantColors` | with Fetch product details on: how many variants, the size and colour pickers |
| `variantMinPrice` / `variantMaxPrice` / `inventoryTotal` | with Fetch product details on: the variant price span and summed stock |
| `deliveryMinDays` / `deliveryMaxDays` | with Fetch product details on: the delivery estimate span in days |
| `reviews` | with Fetch product details and Fetch reviews on: up to 20 review texts with rating, author, country and date |
| `isAd` / `position` / `searchTerm` / `scopeKind` | `false` / `3` / `"headphones"` / `"search"` (promoted flag, search rank, the term that produced the row and the scope kind) |
| `scrapedAt` / `detailCarriedForward` | `"2026-01-01T00:00:00Z"` / `true` only when a failed detail read was repaired from the previous run's snapshot |
| `changeType` / `changedFields` / `firstSeenAt` / `lastSeenAt` | incremental mode only: `"UPDATED"` / `["price"]` / when a record was first and most recently seen |

### How to Use

1. Pick a **mode**: `search` (by keyword) or `url` (paste a product, search, category or collection link).
2. Fill in the field for that mode, and narrow with the price filters; they apply in both modes, and a pasted product link is the one exception, it returns that single product in full.
3. Turn on **Fetch product details** if you need the description, variants, gallery, store rating or reviews.
4. Set **Max items** to control run size and cost, then click **Start**.

**Search by keyword:**

```json
{
  "mode": "search",
  "searchTerms": ["headphones"],
  "maxItems": 20
}
```

**Search with details and reviews on:**

```json
{
  "mode": "search",
  "searchTerms": ["headphones"],
  "fetchDetails": true,
  "fetchReviews": true,
  "maxReviews": 20,
  "maxItems": 20
}
```

**Paste a search link, discounted rows only:**

```json
{
  "mode": "url",
  "urls": ["https://www.joom.com/en/search?q=headphones"],
  "onSaleOnly": true,
  "maxItems": 100
}
```

**Paste a single product link:**

```json
{
  "mode": "url",
  "urls": ["https://www.joom.com/en/products/682abb4b90498f0131f1881a"]
}
```

#### Run it from your code

Python:

```python
from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("abotapi/joom-com-scraper").call(run_input={"mode": "search", "searchTerms": ["headphones"], "maxItems": 20})
for product in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(product["title"], product["price"], product["originalPrice"])
```

JavaScript:

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

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('abotapi/joom-com-scraper').call({ mode: 'search', searchTerms: ['headphones'], maxItems: 20 });
const { items } = await client.dataset(run.defaultDatasetId).listItems();
```

Or connect it to Make, Zapier, n8n, Google Sheets or webhooks from the **Integrations** tab.

#### How Max items and Max pages shape a run

**Max items** is the single cap on a run, across every search term and URL; set it to `0` for unlimited. With more than one search term or URL, the cap is shared out evenly up front: each source gets at most its equal share (for example 20 each for two sources and Max items 40), and a share one source does not use is not handed to the others. **Max pages** is an optional safety bound per source, on top of that cap. The marketplace serves about 26 products per page: when a page holds more fresh candidates than the budget left for that source, only the first candidates on that page, in the marketplace's own order, are read this run, and the run's log names how many of that page were kept. The rest of that page is not read this run, and a product cut off this way is also skipped if a later search term or URL in the same run lists it, so overlapping search terms can return fewer rows than Max items allows.

This matters most with **Incremental mode** on a small, recurring **Max items**. The budget counts returned rows across pages (an unchanged row that is suppressed does not use it up, so the walk moves on to the next page), but within one page it is a cut by position: the candidates after the first N on a page are never classified at all this run, even when the first N all turn out unchanged and nothing is returned. A genuine price or discount change on one of them is missed, and the run's summary message does not say it was capped (a run where every candidate it did classify was unchanged reports "N product(s) scanned, nothing changed", the same message a fully complete, unchanged scan produces). Because every run starts from the top of the results again, a later run with the same Max items cuts the page at the same place, so while the products ranked ahead of it stay unchanged, that change can stay unreported run after run. For a recurring, monitored search or URL, set **Max items** to `0` or to at least the size of the tracked scope so a page is never sliced mid-way.

#### Resume and recurring updates

- **Resume** (`resumeFromRunId`) continues one interrupted or capped run: paste its run or dataset ID and the actor skips everything already collected there, so you don't pay twice.
- **Incremental mode** (`incrementalMode`) is for running the same search or URL again and again (for example daily) and getting only what changed. Each record classifies `NEW`, `UPDATED` (with `changedFields`; a price move, a discount change, a stock change or new reviews on a discount marketplace ARE reported as UPDATED, since that is exactly what a monitor watches for), `UNCHANGED` (suppressed and not billed unless `emitUnchanged` is on), `REAPPEARED`, or `EXPIRED` (only after a run that scanned the whole tracked scope: never when Max items or Max pages capped the walk short, never with Resume, and never after a refusal). Image URLs never mark a row UPDATED on their own. `stateKey` names or shares the stored state, so two differently configured searches never mix their history.

### Send results into your apps (MCP connectors)

Optionally pipe the scraped results into the apps you already use, via Model Context Protocol (MCP) connectors. This is an extra delivery step **after** the scrape: the Apify dataset is never changed.

**What gets written to the connector:** a condensed, human-readable **summary** of each record, not the full JSON. Each item becomes one entry with a **title** and its key fields flattened to plain text. The **complete record always stays in the Apify dataset**.

1. Authorize a connector once under **Apify → Settings → Integrations** (Notion, Linear, Airtable, or Apify).
2. Select it in the **"Pipe results into your apps"** input field. (If the picker is empty, you haven't authorized a connector yet.)
3. For **Notion**, also set `notionParentPageUrl` to the page where items should be created.

The connection is mediated by Apify's MCP proxy, so this actor never sees your third-party credentials. Leave the field empty to skip.

### Input Parameters

| Parameter | Type | Default | Description |
| --- | --- | --- | --- |
| `mode` | string | `search` | `search` (by keyword) or `url` (paste marketplace links). |
| `searchTerms` | array | `["headphones"]` | Search mode: one or more terms to search for, each scraped independently. |
| `urls` | array | sample | URL mode: product, search, category or collection links; each pasted URL decides its own scope. |
| `minPrice` | integer | (none) | Only keep rows whose selling price is at least this much, in the row's currency. |
| `maxPrice` | integer | (none) | Only keep rows whose selling price is at most this much, in the row's currency. |
| `onSaleOnly` | boolean | `false` | Only keep rows with a discount (selling price below the original price). |
| `fetchDetails` | boolean | `true` | Fetch each item's product record: description, variant summary, gallery, store rating and rating histogram. Charged once per record. |
| `fetchReviews` | boolean | `true` | Also read each product's review list into the nested reviews field, up to Max reviews per product. Review pages add one fee per started block of 10 delivered reviews. |
| `maxReviews` | integer | `20` | How many reviews to keep per product. `0` skips review text while keeping the rating histogram and count. Each started block of 10 delivered reviews adds one review pages fee. |
| `maxItems` | integer | `20` | The single cap on this run, across all search terms and URLs. `0` = unlimited. |
| `maxPages` | integer | `0` | Safety bound on result pages walked per search term or URL. `0` = no page limit (Max items still applies). |
| `ignoreFieldsForChanges` | array | (none) | Incremental mode only: extra field names to keep out of the change fingerprint. Price, discount, stock and rating fields are never ignored. |
| `resumeFromRunId` | string | (none) | Continue one interrupted run without returning or charging for records it already collected. |
| `incrementalMode` | boolean | `false` | Turn on for recurring monitoring of the same search or URL: later runs return only new, changed and reappeared records. |
| `stateKey` | string | (none) | Name or share an incremental-mode monitoring campaign's stored state. |
| `emitUnchanged` | boolean | `false` | Also return (and bill) records that have not changed since the last run. |
| `emitExpired` | boolean | `false` | Also return (and bill) records that were tracked before but are no longer found, once a run fully scans the tracked scope. |
| `mcpConnectors` | array | (none) | Optional: send a summary of each record to apps you authorized under Integrations. |
| `notionParentPageUrl` | string | (none) | Notion connector only: page under which record pages are created. |
| `maxNotifyListings` | integer | `50` | Cap on records written to each connector per run. |
| `proxy` | object | Apify Proxy | Connection settings. Residential is the default and the most reliable choice for this marketplace. |

### Output Example

> Sample shape: values are illustrative placeholders, not from a live record.

```json
{
  "recordId": "joom:682abb4b90498f0131f1881a",
  "rowType": "product",
  "productId": "682abb4b90498f0131f1881a",
  "url": "https://www.joom.com/en/products/682abb4b90498f0131f1881a",
  "title": "Sample Wireless Headphones with Charging Case",
  "price": 8.78,
  "currency": "USD",
  "originalPrice": 10.97,
  "onSale": true,
  "discountPercent": 20.0,
  "category": "Electronics",
  "categoryId": "1597236000000000000-00-0-0-0000000000",
  "storeId": "60ce1650947dba277c31869a",
  "storeName": "Sample Store",
  "storeRating": 4.6,
  "averageRating": 4.7,
  "reviewCount": 2000,
  "reviewCountText": " / 2,000+",
  "ratingDistribution": {"all": 2000, "fiveStars": 1500, "fourStars": 283},
  "inStock": true,
  "isAd": false,
  "imageUrl": "https://images.example.com/products/sample-1.jpg",
  "imageUrls": [
    "https://images.example.com/products/sample-1.jpg",
    "https://images.example.com/products/sample-2.jpg"
  ],
  "description": "A sample product description with size and material details.",
  "minPrice": 4.0,
  "maxPrice": 5.0,
  "shippingMinPrice": 3.0,
  "shippingMaxPrice": 3.0,
  "shippingCurrency": "USD",
  "variantsCount": 105,
  "variantSizes": ["S", "M", "L", "XL"],
  "variantColors": ["Red", "Blue"],
  "variantMinPrice": 5.0,
  "variantMaxPrice": 9.0,
  "inventoryTotal": 10500,
  "deliveryMinDays": 6,
  "deliveryMaxDays": 16,
  "reviews": [
    {"review_id": "r-1", "review_text": "Great value", "review_author": "Sample Reviewer", "review_country": "France", "review_stars": 5, "review_likes": 1, "review_createdAt": "2026-01-01T00:00:00Z", "review_size": "M", "review_sizeFit": "Fits true to size"}
  ],
  "position": 3,
  "searchTerm": "headphones",
  "scopeKind": "search",
  "detailCarriedForward": false,
  "scrapedAt": "2026-01-01T00:00:00Z"
}
```

With **Incremental mode** on, a row also carries `changeType`, `changedFields`, `firstSeenAt` and `lastSeenAt`.

### Plan Requirement

The default proxy setting works out of the box: residential is the default and the most reliable choice, since the marketplace answers residential exits most consistently. The actor rotates connections automatically when one is refused; change the Proxy configuration only if a run reports it could not read any results. Fetch product details adds a paid surcharge, charged once per record at most; with Fetch reviews on, review pages add one more fee per started block of 10 delivered reviews. The price pair, store, category and rating are on every row either way.

### FAQ

#### How much does it cost?

You pay per product record returned, plus an optional once-per-record surcharge when Fetch product details is on. With Fetch reviews on, each started block of 10 delivered reviews adds a small review pages fee, so the fee scales with how many reviews you actually pull (the Max reviews per product cap bounds it). The **Pricing** tab shows the current rates. Use **Max items** to cap the cost of any run.

#### Is it legal to scrape Joom?

This actor collects only publicly available product data. You are responsible for how you use it: follow the marketplace's terms and the laws that apply to you, and get legal advice if you plan commercial redistribution. Product names, prices and stock levels are generally facts, but images and descriptions may be subject to third-party rights.

#### Can I get only new or changed products on a schedule?

Yes. Schedule the actor from the **Schedules** tab and turn on **Incremental mode**. Each run then returns only new, updated and reappeared records; unchanged ones are suppressed and not billed unless **Emit unchanged** is on.

#### Why did a run return fewer products than I expected?

**Max items** is the single cap on a run, across every search term and URL, and with several sources it is split evenly between them up front: with two search terms and Max items 40, each term returns at most 20, even if the other term finds nothing. When a page holds more fresh candidates than a source's remaining budget, only the first candidates on that page, in the marketplace's own order, are read, and a product cut off that way is also skipped by any later search term in the same run that lists it. Raise Max items, or set it to `0`, to read further. With **Incremental mode** on for a recurring search, keep Max items at `0` or at least the size of the whole tracked scope: a candidate cut off mid-page is not classified at all that run, so a genuine change on it can be missed without the run looking capped from its own summary message, and later runs with the same Max items cut the page at the same place, so it can stay missed until the products ranked ahead of it change or Max items is raised.

#### Why did my run fail instead of returning an empty dataset?

If the marketplace refuses every request, the run stops with a clear message so "nothing matched" is never confused with "nothing could be read". The marketplace gates some exits with a bot check in waves; run it again in a few minutes, or change the Proxy configuration. If only some search terms or URLs could be read, you still get what was found, and the run's log shows which source could not be read (when nothing at all was found, the status message also gives the count of sources that could not be read).

#### What's the difference between Resume and Incremental mode?

**Resume** (`resumeFromRunId`) continues ONE specific interrupted or capped run: paste its run or dataset ID and this run skips everything it already collected there. **Incremental mode** is for running the SAME search or URL again and again (for example daily) and getting only what changed; it keeps its own state per search, independent of any one run.

#### Can I use it with AI agents or MCP?

Yes. Call it from any Apify integration or MCP client, and use the connector field to push results into Notion, Linear or Airtable.

### 🔗 More scrapers you might like

Pair this actor with these related scrapers from the same team:

<table>
<tr><td>🧩 <a href="https://apify.com/abotapi/asos-com-scraper"><b>ASOS Scraper</b></a><br>Scrape ASOS by keyword, category or URL. Every row carries the selling price and the...</td><td>🛒 <a href="https://apify.com/abotapi/thegioididong-scraper"><b>Thegioididong Scraper</b></a><br>Scrape thegioididong.com products with full specifications, current &amp; original price...</td></tr>
<tr><td>🧩 <a href="https://apify.com/abotapi/tiktok-shop-scraper"><b>TikTok Shop Scraper</b></a><br>Scrape TikTok Shop by keyword, category or product URL. Extract prices, discounts, sales...</td><td>👗 <a href="https://apify.com/abotapi/yesstyle-com-scraper"><b>YesStyle Scraper</b></a><br>Scrape YesStyle products by keyword or URL. Extract prices, discounts, ratings, stock...</td></tr>
<tr><td>🔌 <a href="https://apify.com/abotapi/dienmayxanh-scraper"><b>Dienmayxanh Scraper</b></a><br>Scrape dienmayxanh.com home appliances and electronics with full specifications, current...</td><td>👗 <a href="https://apify.com/abotapi/otto-de-scraper"><b>OTTO.de Scraper</b></a><br>Scrape OTTO.de products by search or URL. Extract prices, discounts, variants...</td></tr>
</table>

👉 [Browse all abotapi scrapers](https://apify.com/abotapi)

### 💬 Support & custom scrapers

- 🐞 **Found a bug or a missing field?** Open a ticket on the [Issues tab](https://apify.com/abotapi/joom-com-scraper/issues/open). We usually reply within hours.
- 🛠️ **Need another site, extra fields or a private build?** Email <contact@abotapi.com> or message [Telegram @abotapi](https://t.me/abotapi).
- ⭐ **Enjoying it?** A quick review on the actor page helps other users find it.

# Actor input Schema

## `mode` (type: `string`):

How to start the scrape. 'search' runs marketplace searches. 'url' processes the marketplace URLs you paste: a product URL is fetched as a single product, and a search, category or collection URL is paged like a search, its own scope deciding the walk. The filters below apply to every walk in both modes; a pasted product URL is the one exception and returns that single product in full.

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

One or more things to search the marketplace for, for example 'headphones', 'dress', 'lamp'. Each term is scraped independently. Search mode only: in URL mode the scope is read out of each pasted URL instead. Leave this empty and the run browses the current offers with only the filters applied.

## `urls` (type: `array`):

Paste product URLs (/en/products/...) or search URLs (/en/search?q=...), category URLs (/en/search/c....) or collection URLs (/en/best/...). A product URL ignores paging and returns that one product in full.

## `minPrice` (type: `integer`):

Only keep rows whose selling price is at least this much, in the row's currency. Applied to the rows this run reads. Applies in BOTH search mode and URL mode.

## `maxPrice` (type: `integer`):

Only keep rows whose selling price is at most this much, in the row's currency. Applied to the rows this run reads. Applies in BOTH search mode and URL mode.

## `onSaleOnly` (type: `boolean`):

Only keep rows whose selling price is below the original price, that is rows with a discount. Applied to the rows this run reads. Applies in BOTH search mode and URL mode.

## `fetchDetails` (type: `boolean`):

Fetch each item's product record for the description, variant summary, image gallery, store rating and rating histogram. Slower, and charged once per record. Leave off for a fast crawl: identity, prices, discount and rating are included either way.

## `fetchReviews` (type: `boolean`):

Only applies when Fetch product details is on. Also read each product's review list into the nested reviews field, up to Max reviews per product. Review pages are billed separately from the details surcharge: one review pages fee per started block of 10 delivered reviews.

## `maxReviews` (type: `integer`):

Only applies when Fetch reviews is on. How many reviews to keep per product, newest first as the marketplace serves them. Set 0 to skip review text while keeping the rating histogram and review count. Each started block of 10 delivered reviews adds one review pages fee.

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

The single cap on this run: stop after collecting this many records across all search terms and URLs. Set 0 for unlimited.

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

Safety bound on how many result pages to walk per search term or URL. Leave empty (0) for no page limit: the run then stops at Max items, not here. Does not impose a separate cap below Max items.

## `proxy` (type: `object`):

Leave the default for the most reliable run. The marketplace answers residential exits most consistently, and datacenter exits are challenged more often. Change it only if a run reports that it could not read any results.

## `resumeFromRunId` (type: `string`):

Paste a previous run ID or dataset ID to continue a large crawl without returning or charging for records already collected there. Use this after an interrupted or capped run. For recurring monitoring of the same search, use Incremental mode below instead.

## `incrementalMode` (type: `boolean`):

Turn this on for daily or weekly recurring monitoring of the same search, for example a price watch. The first run returns everything matching as NEW. Later runs normally return only NEW, UPDATED and REAPPEARED records. Price moves, discount changes, stock changes and new reviews ARE reported as UPDATED: on a discount marketplace they are the signal, not noise. Image URLs never mark a row UPDATED on their own. Turn on Emit unchanged or Emit expired only when you also want those rows returned (and billed). State is kept separately per search, URL and filter setup; use State key to name or deliberately share a monitoring campaign. To continue one specific interrupted run instead, use Resume from a previous run above.

## `stateKey` (type: `string`):

Optional. Name this monitoring campaign to keep its state stable, or to deliberately share state across differently configured runs. Leave empty to let the actor derive a key automatically from the search terms, URLs and filters, so two different searches never mix state.

## `emitUnchanged` (type: `boolean`):

Off by default. Turn on to also return records that have not changed since the last run, marked UNCHANGED. This returns, and bills, extra rows you already have, so leave it off unless you specifically want a full snapshot every run.

## `emitExpired` (type: `boolean`):

Off by default. Turn on to also return records that were present in a previous run but are no longer found, marked EXPIRED. Only produced once a run has fully scanned the tracked search: not when Max items capped it, not when Resume was used, and not when the run was refused. This returns, and bills, extra synthetic rows, so leave it off unless you need expiry tracking.

## `ignoreFieldsForChanges` (type: `array`):

Incremental mode only. Extra field names to keep out of the change fingerprint, on top of the built-in image URL ignore list. Use this when a field moves on every run without the product changing. Price, discount, stock and rating fields are never ignored: on a discount marketplace they are the signal.

## `mcpConnectors` (type: `array`):

Optionally send results into the apps you already use, via Model Context Protocol (MCP) connectors. Authorize one under Apify, Settings, API and Integrations, then select it here. Notion gets a page per record; other connectors get a best-effort write or digest. Each connector receives a condensed summary per record, not the full record; the complete record always stays in the dataset. Leave empty to skip; this never changes the dataset output. Supported: Notion (https://mcp.notion.com/mcp), Linear (https://mcp.linear.app/sse), Airtable (https://mcp.airtable.com/mcp), Apify (https://mcp.apify.com).

## `notionParentPageUrl` (type: `string`):

URL or id of the Notion page under which record pages are created. Required to enable the Notion export; ignored by other connectors.

## `maxNotifyListings` (type: `integer`):

Cap on records written to each connector per run. Does not affect the dataset.

## Actor input object example

```json
{
  "mode": "search",
  "searchTerms": [
    "headphones"
  ],
  "urls": [
    "https://www.joom.com/en/search?q=headphones",
    "https://www.joom.com/en/products/682abb4b90498f0131f1881a",
    "https://www.joom.com/en/search/c.1597236299943220874-45-2-2-1385917236",
    "https://www.joom.com/en/best/printing-t-shirt"
  ],
  "onSaleOnly": false,
  "fetchDetails": true,
  "fetchReviews": true,
  "maxReviews": 20,
  "maxItems": 20,
  "maxPages": 0,
  "proxy": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  },
  "incrementalMode": false,
  "emitUnchanged": false,
  "emitExpired": false,
  "ignoreFieldsForChanges": [],
  "maxNotifyListings": 50
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

## `detail` (type: `string`):

No description

## `reviews` (type: `string`):

No description

## `changes` (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 = {
    "mode": "search",
    "searchTerms": [
        "headphones"
    ],
    "urls": [
        "https://www.joom.com/en/search?q=headphones",
        "https://www.joom.com/en/products/682abb4b90498f0131f1881a",
        "https://www.joom.com/en/search/c.1597236299943220874-45-2-2-1385917236",
        "https://www.joom.com/en/best/printing-t-shirt"
    ],
    "fetchDetails": true,
    "fetchReviews": true,
    "maxReviews": 20,
    "maxItems": 20,
    "proxy": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    },
    "incrementalMode": false,
    "emitUnchanged": false,
    "emitExpired": false,
    "ignoreFieldsForChanges": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("abotapi/joom-com-scraper").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 = {
    "mode": "search",
    "searchTerms": ["headphones"],
    "urls": [
        "https://www.joom.com/en/search?q=headphones",
        "https://www.joom.com/en/products/682abb4b90498f0131f1881a",
        "https://www.joom.com/en/search/c.1597236299943220874-45-2-2-1385917236",
        "https://www.joom.com/en/best/printing-t-shirt",
    ],
    "fetchDetails": True,
    "fetchReviews": True,
    "maxReviews": 20,
    "maxItems": 20,
    "proxy": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
    "incrementalMode": False,
    "emitUnchanged": False,
    "emitExpired": False,
    "ignoreFieldsForChanges": [],
}

# Run the Actor and wait for it to finish
run = client.actor("abotapi/joom-com-scraper").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 '{
  "mode": "search",
  "searchTerms": [
    "headphones"
  ],
  "urls": [
    "https://www.joom.com/en/search?q=headphones",
    "https://www.joom.com/en/products/682abb4b90498f0131f1881a",
    "https://www.joom.com/en/search/c.1597236299943220874-45-2-2-1385917236",
    "https://www.joom.com/en/best/printing-t-shirt"
  ],
  "fetchDetails": true,
  "fetchReviews": true,
  "maxReviews": 20,
  "maxItems": 20,
  "proxy": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  },
  "incrementalMode": false,
  "emitUnchanged": false,
  "emitExpired": false,
  "ignoreFieldsForChanges": []
}' |
apify call abotapi/joom-com-scraper --silent --output-dataset

```

## MCP server setup

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

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/opmL6vGDljVkD2y9e/builds/Zvkm9YgHb7uwVYkMx/openapi.json